Push images by digest to skip per-arch tags#31
Merged
richturner merged 2 commits intomainfrom May 6, 2026
Merged
Conversation
Replace the per-arch tag scaffolding (`develop-amd64`, `develop-arm64`,
`develop-amd64-slim`, `develop-arm64-slim`, plus the versioned variants)
with buildx push-by-digest. Each per-arch image is uploaded to Docker
Hub addressed only by content digest; the digest is then handed to
`docker buildx imagetools create` to assemble the final multi-arch
manifest. Net effect on Docker Hub: only the multi-arch tags
(`develop`, `develop-slim`, `<version>`, `<version>-slim`, `latest`,
`latest-slim`) are ever published — no per-arch tags are created at any
point.
The base image build now uses a multi-output buildx invocation
(`type=docker` for daemon load + `type=image,push-by-digest=true,name-canonical=true,push=true`
for the registry push). slim-toolkit still operates on the daemon
image, then a small `Dockerfile.passthrough` (`FROM \${SRC}`) is built
through the docker driver builder so its `--build-context
docker-image://` reference can resolve from the host daemon, exporting
by digest only. Digests cross job boundaries via `actions/upload-artifact`
+ `actions/download-artifact`. PR builds are unchanged in shape: build
+ scan + slim run, nothing is pushed.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
richturner
approved these changes
May 6, 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.
Closes #30.
Summary
develop-amd64,develop-arm64,develop-amd64-slim,develop-arm64-slim, plus versioned variants) with buildx push-by-digest. Per-arch images are now uploaded by content digest only;docker buildx imagetools createassembles the multi-arch tags from those digests. Result: onlydevelop/develop-slim/<version>/<version>-slim/latest/latest-slimever appear on Docker Hub.type=dockerfor daemon load + scan/slim, plustype=image,push-by-digest=true,name-canonical=true,push=truefor the registry push, withprovenance: falseto keep the merged manifest clean).Dockerfile.passthrough(FROM ${SRC}) built through thedockerdriver builder so--build-context docker-image://local-ci-image-slim:latestresolves from the host daemon (the defaultdocker-containerdriver can't see daemon-only images).actions/upload-artifact@v4.6.2+actions/download-artifact@v4.3.0. PR builds are unchanged in shape (build + scan + slim run, nothing pushed);create_manifestsis still gated on non-PR.