Drop registry cache imports that only burned pull quota - #9
Merged
Conversation
Every registry manifest fetch counts against Docker Hub's hourly pull quota, and the master publish has been starving on it: each push attempt landed all but the last couple of tags per shard before the window ran dry, cycle after cycle. Two imports were costing quota without buying anything: - The push template's --cache-from lines. dave push re-runs a build whose every layer is already in the local image store of the same daemon that just built and tested it, so the rebuild fully cache-hits locally and the registry imports were pure overhead -- 2-3 manifest fetches per tag per attempt. - The build template's unsuffixed legacy-ref fallback from before the per-arch cache split. One stale-cache lookup per tag per run for a cache that is weeks old. The arch-scoped and PR-scoped imports in the build template stay: those are what let a retry rebuild to identical image IDs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
What
The master publish keeps starving on Docker Hub's hourly pull quota: every attempt lands all but the last couple of tags per shard before the window runs dry, cycle after cycle. Two classes of registry cache imports were spending that quota without buying anything:
--cache-fromlines:dave pushre-runs a build whose every layer already sits in the local image store of the same daemon that built and tested it, so the rebuild fully cache-hits locally — the 2–3 registry manifest fetches per tag per attempt were pure overhead.The arch-scoped and PR-scoped imports in the build template stay — they're what let a retry rebuild to identical image IDs and hit the integration-test skip stamps.
Verification
--cache-from,--cache-tointact); build templates keep exactly the arch + PR-scope imports.🤖 Generated with Claude Code