docs: document sibling-container networking gotcha#142
Open
truffle-dev wants to merge 1 commit into
Open
Conversation
Sibling containers default to the bridge network and are unreachable from phantom; document the --network phantom_phantom-net launch flag and the docker network connect after-the-fact form, with a note on container-name DNS resolution and the host-port-binding tradeoff. Closes ghostwright#134
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.
Closes #134.
Summary
The Phantom stack runs on a private
phantom_phantom-netbridge, but a sibling container launched with a plaindocker runlands on Docker's defaultbridgenetwork and is unreachable from phantom. The friction is consistent (the issue body has a full repro) and the existing "Docker socket permissions" section indocs/getting-started.mdmentions sibling containers without addressing reachability.This PR adds a "Networking for sibling containers" subsection right after Docker socket permissions, covering the four points called out in the issue:
--network phantom_phantom-netat launch,docker network connect …after the fact).bridge+-p, expect to lose reachability from phantom.CLAUDE.mdgets a one-line extension on the existing "Docker socket mount (not DinD)" bullet pointing readers at the new section, so the gotcha surfaces where an agent reading its instructions would actually encounter the trap.Docs-only, no behavior changes.