feat(workflows): docker-build with a layer cache that outlives the runner - #80
Merged
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
…nner
Disposable runners rebuild every layer from scratch: the catalogue had a
Trivy scan for containers and no way to build one. docker-build.yml puts
the BuildKit cache in a registry ref ({image}/buildcache by default, free
storage on ghcr.io today) or in the Actions cache, shared across runs,
repositories and runner kinds; hosted and docker-capable fleet classes use
the same call. Pins registered in the tool registry, the cache-contract
declares build-push-action as an explicit no-input-no-cache producer, the
example pins by sha and names its runner, generated docs follow.
The fleet-local zot variant of the cache ref stays open in the estate
ledger: writing buildcache to the member registry needs broker-minted
credentials, which is fleet-side work, and ghcr serves the pattern today.
Claude-Session: https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF
rldyourmnd
force-pushed
the
feat/docker-build-with-a-registry-cache
branch
from
September 1, 2026 08:04
cef35b3 to
162cc7e
Compare
…h-a-registry-cache
zizmor's permissions rule wants the reason next to the grant, which is the house style everywhere else in this catalogue. Claude-Session: https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF
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.
New reusable build workflow: registry layer cache ({image}/buildcache, free on ghcr today) or type=gha, one call for hosted and docker-capable fleet runners, digest output. Full registration: tool pins, cache-contract producer (no input — no cache), routed capability, sha-pinned example, regenerated docs; validate_all core OK locally.
https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF