Fix release workflow: manifest list conflict on major-version arch tags#63
Merged
Merged
Conversation
…ic repos GHCR will not overwrite a manifest-list tag with a single-arch image push, causing docker manifest create to fail with "is a manifest list". Fix by only pushing the exact version tag to -amd64/-arm64 repos; both manifest lists (:VERSION and :MAJOR) now reference the exact-version arch images. Also fix deprecated LABEL syntax warnings in package/Dockerfile.
Newer Docker/BuildKit wraps single-platform builds in an OCI index when it attaches a provenance attestation manifest. This makes every pushed image a manifest list, causing docker manifest create to fail with "is a manifest list". Setting BUILDX_NO_DEFAULT_ATTESTATIONS=1 prevents the attestation wrapper so arch-specific images are pushed as plain single-platform manifests.
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.
Summary
crypteia-extension-amzn-amd64:2andcrypteia-extension-debian-amd64:2stayed as manifest lists from a prior release, causingdocker manifest createto fail with "is a manifest list":2) from arch-specific image builds/pushes — those repos now only receive the exact version tag (:2.2.1):2.2.1and:2) reference the exact-version arch images, which are always fresh tagsdocker manifest rm … || truebefore eachdocker manifest createto clear stale local manifest cache entriesLABEL key value→LABEL key=valuesyntax inpackage/Dockerfile(removes two build warnings)Test plan
debianandamznjobs pass without "is a manifest list" error:VERSIONand:MAJORare created correctly in GHCR