Use inspectNetworkCmd to get the gateway's IP#2151
Merged
Conversation
Member
|
I've tested this with our internal derivative of dind-drone-plugin and am happy that it behaves consistently in even our slightly complicated DinD setup 😄. |
rnorth
approved these changes
Dec 19, 2019
delete-merged-branch
bot
deleted the
resolve_docker_host_ip_via_network_inspect
branch
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
2 participants
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.
To avoid running a container with
ip|awk, we can simply inspect thebridgenetwork instead.This idea was discovered while hacking on testcontainers/testcontainers-rs#139