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
set resolver to dockers internal dns for first 30 seconds #1002
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1002 +/- ##
=======================================
Coverage 78.34% 78.34%
=======================================
Files 63 63
Lines 3247 3247
=======================================
Hits 2544 2544
Misses 703 703 Continue to review full report at Codecov.
|
Test summaryRun details
View run in Cypress Dashboard ➡️ Failures
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
Pushed to deepdream, no longer getting 502 error, But there is something else wrong now, swagger ui is blank with lots of JS errors like:
|
@rwblair I think theres' something wrong w/ nginx bc it doesn't seem to be loading the json files and css files for swagger ui. looks like maybe they're routed instead to the wrong container (neuroscout?). can you take a look? |
^~ vs ^ vs none? otherwise let's merge this so it fixes swagger-ui and we can fix the problem of restarting nginx (when swagger fails) in another PR later. |
If the swagger containers hostname wouldn't resolve nginx would fail to start. I put in the set directive by its proxypass to get around nginx trying to do the hostname lookup on startup. Nginx was complaining about not having a resolver when you visited /api/swagger. Made change according to this:
https://sandro-keil.de/blog/let-nginx-start-if-upstream-host-is-unavailable-or-down/