Fix local development docker compose nginx config to work properly with non-docker-for-desktop setups #612
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…or-desktop setups
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With most non-docker-for-desktop docker setups (for example native docker on linux) the host.docker.internal domain is not properly resolved at nginx startup. The typical "fix" is to instruct nginx explicitly to use the docker embedded dns resolver at 127.0.0.11 dynamically at request time by specifying the resolver in the config as well as putting the actual target for the proxy_pass directive behind a variable (otherwise nginx will attempt to resolve the address at startup and never again after that)