fix(build): disable BuildKit attestations to fix multi-arch manifest creation#242
Merged
JesperTerkelsen merged 1 commit intomainfrom Feb 19, 2026
Merged
Conversation
…creation BuildKit v0.26.3+ generates attestation manifests by default, which turns single-platform image pushes into manifest lists. This causes `docker manifest create` to fail with "is a manifest list" error since you can't nest manifest lists. Setting `provenance: false` alone is insufficient with newer BuildKit. Adding `BUILDX_NO_DEFAULT_ATTESTATIONS=1` and `sbom: false` ensures each per-arch image is pushed as a plain single-platform image. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Member
|
I might not agree here -lets figure out if this is a real fix or not |
JesperTerkelsen
approved these changes
Feb 19, 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.
Summary
BUILDX_NO_DEFAULT_ATTESTATIONS=1env var andsbom: falseto the build step incomponent-build.ymldocker manifest createfailing with"<image>-amd64 is a manifest list"errorProblem
BuildKit v0.26.3+ (shipped with buildx v0.31.1 on
ubuntu-24.04runners) generates attestation manifests by default, even whenprovenance: falseis set. This turns each single-platform image push into a manifest list (containing the image + attestation manifest), which causesdocker manifest createto fail because you can't nest manifest lists.Example failure: https://github.com/monta-app/service-ocpp/actions/runs/22174445891/job/64119854148
Test plan
service-ocppafter merging to verify the multi-arch manifest step succeeds🤖 Generated with Claude Code