Docker docs: bind the host port to 127.0.0.1 explicitly - #181
Closed
bendichter wants to merge 1 commit into
Closed
Conversation
A bare -p 8888:8888 binds all interfaces, and on macOS it coexists with a local Jupyter server already listening on 127.0.0.1:8888, so the browser silently reaches the wrong server and shows a confusing 404. Binding 127.0.0.1 explicitly keeps the container off network interfaces and turns a port collision into a loud "address already in use" error. Found during the pilot pull-and-run validation. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Index page previewA preview of the generated Last updated: commit |
Member
Author
Member
Author
|
Closing: the commit landed on master via #182. |
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
1 participant
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.
Follow-up to #180, found while validating the pilot image on a laptop. A bare
-p 8888:8888binds all interfaces, and on macOS it can coexist with a local Jupyter server already listening on127.0.0.1:8888. The browser then reaches the local server instead of the container and shows a confusing 404, because the local server does not know the container's token and may not serve/labat all. Our target users are exactly the people most likely to have a Jupyter server on port 8888.Binding the host side to
127.0.0.1explicitly fixes both halves: the server stays off network interfaces, and a genuine port collision fails loudly with "address already in use" instead of silently splitting the traffic. The docs now also tell users how to pick an alternate host port.🤖 Generated with Claude Code