fix: install docker-mcp release instead of compiling it - #24
Merged
Merged
Conversation
Building docker-mcp from source broke when Go's floating `latest` selector advanced past 1.27 and mcp-gateway's vendored x/net no longer resolved (undefined http2.TrailerPrefix). Consuming the upstream release tarball removes that coupling, drops the ~6.8k-file clone and ~60s compile, and lets DOCKER_MCP_VERSION pin or roll back the plugin version explicitly.
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.
Building docker-mcp from source broke when Go's floating
latestselector advanced past 1.27 and mcp-gateway's vendored x/net no longer
resolved (undefined http2.TrailerPrefix). Consuming the upstream
release tarball removes that coupling, drops the ~6.8k-file clone and
~60s compile, and lets DOCKER_MCP_VERSION pin or roll back the plugin
version explicitly.