fix: restore provenance: false in Docker builds#234
Merged
gabrielanhaia merged 1 commit intomainfrom Feb 18, 2026
Merged
Conversation
The `provenance: false` setting was accidentally removed in b6f6177 ("remove Docker layer caching support") along with the caching config. Without it, `docker/build-push-action@v6` creates manifest lists (with provenance attestations) for per-arch images. This causes `docker manifest create` to fail with "is a manifest list" because Docker CLI cannot nest manifest lists.
chandrashekar-dhar
approved these changes
Feb 18, 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
Restores the
provenance: falsesetting incomponent-build.ymlthat was accidentally removed in b6f6177 ("remove Docker layer caching support").Problem
All Kotlin service deploys are failing at the "Create Multi-Arch Manifest" step with:
docker/build-push-action@v6enables provenance attestations by default, which turns per-architecture images into manifest lists.docker manifest createcannot nest manifest lists, so the multi-arch manifest creation fails.Fix
Re-add
provenance: falseto the build step. This was originally added in f847a12 and removed by accident in b6f6177 when the caching config was cleaned up.