Repository navigation
Use buildx imagetools to assemble multi-arch manifests - #245
Merged
Merged
Conversation
docker manifest push re-serializes each child manifest before upload. The amd64 per-arch images are pushed by buildx with 2-space indented JSON while the legacy docker manifest tool re-marshals to 3-space, changing the bytes and therefore the digest. The pushed child landed under a new digest while the manifest list still referenced the original, so the registry rejected the list with "manifest blob unknown: blob unknown to registry". docker buildx imagetools create copies children by digest without re-serializing, so digests stay stable. It also keeps no local manifest store, avoiding the unbounded growth of ~/.docker/manifests left behind by "docker manifest push --purge" on failed pushes. Install the buildx CLI plugin in the app image since it only shipped Debian's docker.io package without buildx.
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
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.
docker manifest push re-serializes each child manifest before upload. The amd64 per-arch images are pushed by buildx with 2-space indented JSON while the legacy docker manifest tool re-marshals to 3-space, changing the bytes and therefore the digest. The pushed child landed under a new digest while the manifest list still referenced the original, so the registry rejected the list with "manifest blob unknown: blob unknown to registry".
docker buildx imagetools create copies children by digest without re-serializing, so digests stay stable. It also keeps no local manifest store, avoiding the unbounded growth of ~/.docker/manifests left behind by "docker manifest push --purge" on failed pushes.
Install the buildx CLI plugin in the app image since it only shipped Debian's docker.io package without buildx.