chore(docker): decouple compose from the metamcp network - #1
Merged
Conversation
The compose file required an external network created by another project (metamcp_metamcp-network). That project no longer exists, so `up -d` now fails for everyone, and it was never reproducible outside one machine to begin with. Drops the external network and documents joining one as an optional block. The server still binds 127.0.0.1:3900; a client points at /mcp. README wording follows. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0149Mg7kTnE3eKwmCag5KEcY
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.
Summary
docker/compose.yamldeclared anexternal: truenetwork namedmetamcp_metamcp-network, created by a separate compose project on one machine. That project was torn down, sodocker compose up -dnow fails outright — and the coupling was never reproducible for anyone else in the first place.What changes
127.0.0.1:3900as before; clients point athttp://localhost:3900/mcp.No image, runtime, port or healthcheck changes.
docker compose configvalidates.🤖 Generated with Claude Code
https://claude.ai/code/session_0149Mg7kTnE3eKwmCag5KEcY