-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
frontend started at random port #1001
Comments
This is expected, as the frontendproxy exposes the port 8080 and all access to the demo app is through the envoy proxy. See https://opentelemetry.io/docs/demo/architecture/ |
Hello, Thanks, |
Hello Sahil,
This works for me. |
This worked for me... frontend-proxy no longer crashing and able to get to the frontend on http://localhost:8080. Now onto the 'ConnectionResetError: [Errno 104] Connection reset by peer' errors I'm getting from load-generator. |
I'm getting the same error from |
Closing this as the initial issue is resolved |
Question
Use Github Discussions.
Hi, I used the docker compose and seems like frontend service is starting at a random port. Anyone saw similar issue?
any idea what I am doing wrong?
Commands used:
git clone https://github.com/open-telemetry/opentelemetry-demo.git
cd opentelemetry-demo/
sudo docker-compose up --no-build -d
OS: AmazonLinux - EC2
docker --version --> Docker version 20.10.25, build b82b9f3
docker-compose --version --> Docker Compose version v2.20.2
Thanks,
Sahil
The text was updated successfully, but these errors were encountered: