Skip to content

build: disable buildkit attestations on the tiered images - #13

Merged
daniel-rossier merged 1 commit into
mainfrom
build-no-attestations
Nov 15, 2026
Merged

daniel-rossier merged 1 commit into
mainfrom
build-no-attestations

Conversation

@daniel-rossier

Copy link
Copy Markdown
Contributor

What

Buildkit attaches provenance/SBOM attestations by default, so each tiered image (harness/base/project) is a multi-manifest index. GitLab's container registry rejects the attestation manifest blob on push:

error from registry: blob unknown to registry - sha256:a71de42f…

so an image builds fine locally but can't be published. Pass --provenance=false --sbom=false to all three docker build invocations.

Note

This fixes the attestation failure. A separate, server-side limit on the reds-gitlab registry still rejects the base's multi-GB blobs (resumable blob upload invalid) — unrelated to this change; that one needs the registry/proxy upload cap raised by an admin.

Buildkit attaches provenance/SBOM attestations by default, turning each
image into a multi-manifest index. Some registries -- GitLab's among
them -- reject the attestation manifest's blob on push ("blob unknown to
registry"), so a tiered image could be built but not published. These
images carry their own manifest and need no buildkit attestation, so
pass --provenance=false --sbom=false to all three builds.
@daniel-rossier
daniel-rossier merged commit a0b200f into main Nov 15, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant