Conversation
- Pass --network to docker run when ENCORE_DOCKER_NETWORK is set - Fixes encoredev#2382: Postgres containers unreachable in CI environments that use non-default Docker networks (Cloud Build, etc.)
Member
|
Thanks for adding this! I don't think it is enough to just set the network name, we connect to 127.0.0.1 down in clusterStatus, and for this to work I think we need to use the container name instead. So maybe if the docker network env var is set, connect to containerName:port instead of 127.0.0.1:port |
This file contains hidden or 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
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.
Summary
--networktodocker runwhenENCORE_DOCKER_NETWORKis setcloudbuildDocker networkUsage