Skip to content

chore: enable OCI artifact type for attestation manifests#199

Open
gbartolini wants to merge 1 commit intomainfrom
dev/198
Open

chore: enable OCI artifact type for attestation manifests#199
gbartolini wants to merge 1 commit intomainfrom
dev/198

Conversation

@gbartolini
Copy link
Copy Markdown
Contributor

BuildKit's default image exporter does not set artifactType or the OCI 1.1 Referrers subject backlink on attestation manifests. Setting oci-artifact=true on the image exporter adds both, so SBOM and provenance attestations become discoverable through the OCI Referrers API.

oci-mediatypes=true is redundant (BuildKit already defaults it to true when pushing to a registry, which is why the top-level index is already application/vnd.oci.image.index.v1+json) but kept for clarity.

Same fix as cloudnative-pg/cloudnative-pg#10601, mirroring cloudnative-pg/postgres-containers#436.

Closes #198

BuildKit's default image exporter does not set `artifactType` or the OCI
1.1 Referrers `subject` backlink on attestation manifests. Setting
`oci-artifact=true` on the image exporter adds both, so SBOM and
provenance attestations become discoverable through the OCI Referrers API.

`oci-mediatypes=true` is redundant (BuildKit already defaults it to true
when pushing to a registry, which is why the top-level index is already
`application/vnd.oci.image.index.v1+json`) but kept for clarity.

Same fix as cloudnative-pg/cloudnative-pg#10601, mirroring
cloudnative-pg/postgres-containers#436.

Closes #198

Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
@gbartolini gbartolini requested review from a team and NiccoloFei as code owners May 6, 2026 11:07
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.

docker-bake.hcl: emit attestation manifests as OCI artifacts (set oci-artifact=true)

1 participant