Closed medhedho closed 4 years ago
When you run application in a container, the default 127.0.0.1 address used to reach Jaeger no longer works, because it points to the app container namespace, while Jaeger is running on a different IP. You can use env variables to point to Jaeger container. See example https://github.com/jaegertracing/jaeger/blob/master/examples/hotrod/docker-compose.yml
The problem was in the services. I had to remove this from each Dockerfile: -Djava.security.egd=file:/dev/./urandom
thanks for reporting back @medhedho
Hello,
I'm trying to trace this Spring Boot application: "https://developer.okta.com/blog/2019/02/28/spring-microservices-docker" with the "all-in-one" Jaeger container. I added the "opentracing-spring-jaeger-cloud-starter" to every microservice. When I run these microservices without docker (mvn run), I find my traces in the Jaeger UI. But when I use the attached docker-compose file, I don't find them.