build: set record provenance in response#2280
Merged
tonistiigi merged 1 commit intodocker:masterfrom Apr 11, 2024
Merged
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
crazy-max
commented
Feb 23, 2024
436f6c4 to
4a00e0f
Compare
eb6347c to
e0256b6
Compare
crazy-max
commented
Feb 28, 2024
dvdksn
reviewed
Feb 28, 2024
e0256b6 to
16b5bf3
Compare
4c1003b to
6711c97
Compare
This comment was marked as off-topic.
This comment was marked as off-topic.
a1e68ca to
b3585e6
Compare
9e35c6d to
ad85d2f
Compare
Member
Author
|
@tonistiigi Updated to strip |
ad85d2f to
f0b31ce
Compare
f0b31ce to
eba0b61
Compare
tonistiigi
reviewed
Apr 10, 2024
4e034e5 to
29890fa
Compare
tonistiigi
reviewed
Apr 11, 2024
5e29d4b to
fde233d
Compare
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
fde233d to
2e2f9f5
Compare
tonistiigi
approved these changes
Apr 11, 2024
This was referenced Jun 11, 2024
Member
Author
|
@dvdksn Forgot to add docs-followup label on this one 🙈 for |
3 tasks
aevesdocker
pushed a commit
to docker/docs
that referenced
this pull request
Feb 18, 2025
<!--Delete sections as needed --> ## Description Missing documentation for buildx metadata envs ## Related issues or tickets follow up: * docker/buildx#2280 * docker/buildx#2551 ## Reviews <!-- Notes for reviewers here --> <!-- List applicable reviews (optionally @tag reviewers) --> - [ ] Technical review - [ ] Editorial review - [ ] Product review Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
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
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.
follow-up discussion with @tonistiigi
related to #1681
Previously we got
containerimage.buildinfoin the metadata file butbuildinfohas been removed in BuildKit 0.12 (moby/buildkit#3582): https://github.com/moby/buildkit/blob/master/docs/deprecated.md#build-informationThis was useful to see all sources that were used by the build with their exact versions and also the configuration that was passed to the build.
However with the provenance attestation supported since BuildKit v0.11, we have similar (and a "bit" more) information available.
With this change we set the provenance saved along the build record in the metadata file similar to
containerimage.buildinfothat is namedbuildx.build.provenance. Will set minimal provenance by default but can be customized using theBUILDX_METADATA_PROVENANCEenv var.md.json
md.json
md.json