-
Notifications
You must be signed in to change notification settings - Fork 14
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
Docker-compose failing startup #465
Comments
15-Nov-2023 17:41:22.005 SEVERE [http-nio-7000-exec-1] cwms.cda.security.OpenIDAccessManager. Unable to initialize realm. |
hmm, that implements either a network/hostname/port problem or that the api isn't actually waiting for the database to be ready. |
@MikeNeilson Thanks for pointing me to networking. The instructions say: So instead of 127.0.0.1 I used 192.168.206.134 in /etc/hosts 192.168.206.134 is my Private IP, and I can now see the swagger UI! |
It would be good to figure out a way to not need to do that, but given how just utterly picky some of those services are about URLs and docker with address I'm not sure we can. |
Perhaps a bigger font could help future users though. |
I have a PR here to warn about 127.0.0.1 : #466 |
Closing this issue - docker compose is working for me -- below is my writeup. https://github.com/USACE/cwms-data-api/wiki/How-to-use-Docker%E2%80%90compose-with-a-windows-Client |
@rripken and @ktarbet were having issues getting the docker-compose to startup in their development environments. The specific errors can be added to the description or as comments.
The text was updated successfully, but these errors were encountered: