fix: use COPY --from for mcp-gateway in template stage#3744
Merged
Conversation
aheritier
added
area/mcp
dgageot
approved these changes
Jul 19, 2026
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
2 participants
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.
The
templateDocker build stage fetched the latestdocker-mcpbinary via an unauthenticated GitHub API call, which hit rate limits (HTTP 403) on shared CI runners:curl -fsSL "https://api.github.com/repos/docker/mcp-gateway/releases?per_page=1"The arm64 runner passed because it uses a different IP pool; the amd64 runner hit the 60 req/hr unauthenticated limit.
Fix: replace the 8-line
RUN curl | grep | tarblock with a singleCOPY --from=docker/mcp-gateway:v2instruction — the same pattern already used by the final MCP container stage of the same Dockerfile. No GitHub API calls, no rate-limit exposure.Fixes the flaky CI failure observed on PR #3741.