Document how to access host URL's from within the container #1
Conversation
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.
When developing with a web server running on the host, the browser within the container needs to access the URL that's available only within the host. Adding
--net=hostto thedocker runcommand accomplishes this.See https://docs.docker.com/v1.8/articles/networking/#container-networking for more details, including a warning that "You should use this option with caution." Should a warning like that be included here? When used in a gitlab test runner, for example, the option shouldn't be a problem, but let me know if this PR should be modified to mention that.
Something about this
--net=hostoption should be added to the docs to save others many hours of web searching.