Skip to content

provenance: add custom fields support - #6210

Merged
tonistiigi merged 1 commit into
moby:masterfrom
tonistiigi:provenance-custom-env
Sep 11, 2025
Merged

tonistiigi merged 1 commit into
moby:masterfrom
tonistiigi:provenance-custom-env

Conversation

@tonistiigi

Copy link
Copy Markdown
Member

This allows buildkitd daemon to define additional fields that are added to all the provenance attestations that BuildKit creates (by default from /etc/buildkit/provenance.d/).

These custom fields can provide additional context about the environment BuildKit itself is running (eg. Github workflow) and are not allowed to collide with the trusted fields created by BuildKit itself.

Comment thread cmd/buildkitd/util.go
This allows buildkitd daemon to define additional fields
that are added to all the provenance attestations that
BuildKit creates (by default from /etc/buildkit/provenance.d/).

These custom fields can provide additional context about
the environment BuildKit itself is running (eg. Github workflow)
and are not allowed to collide with the trusted fields created
by BuildKit itself.

Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
@tonistiigi
tonistiigi force-pushed the provenance-custom-env branch from b26874d to 8ecdc0a Compare September 10, 2025 23:57
Comment thread frontend/dockerfile/dockerfile_provenance_test.go
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants