-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Activate docker profile only but read default profile also #232
Comments
Hi @sanme98. Thank you for your feedback. I've the same issue. Maybe it was introduced in a recent Spring Boot and/or Spring Cloud upgrade? The microservices start with the
At startup, they look at their configuration both at
We need to investigate. |
I rollback to a Spring Cloud 2022.0.1 and Spring Boot 3.0.2 commit and I've noticed that config server lookup are reversed. First
|
Hi @arey, I have tried v2.6.7, it is working fine for that version. Maybe it just happens on Spring Boot v3? Thanks. |
This issue comes from the upgrade to Spring Cloud 2022.0.2 to 2022.0.3. On the |
…r compose didn't working with 2022.0.3
* #232 Downgrade to Spring Cloud 2022.0.2 because docker compose didn't working with 2022.0.3
Should be work. Please reopen if not |
* spring-petclinic#232 Downgrade to Spring Cloud 2022.0.2 because docker compose didn't working with 2022.0.3
Hi All,
I ran
docker-compose up
to start the docker, but I found all of the services unable to register on Eureka, it seems connect to Eureka usinghttp://localhost:8761
instead ofhttp://discovery-server:8761
. I cloned this project without any changes. From the log, it seems loaded docker profile and then default profile? Which shouldn't need to load default profile since the Dockerfile only specify docker profile?Below is some part of the log for Customer Services:
May I know how to resolve this error without changing the config yml, so it can still work to run locally and docker?
Noted: If I changed the config yml to below by removed the docker profile, it works.
Thank you.
The text was updated successfully, but these errors were encountered: