ci: fix binfmt gh release #159
Merged
Conversation
This file contains 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
Signed-off-by: CrazyMax <[email protected]>
crazy-max
force-pushed
the
fix-release
branch
2 times, most recently
from
4c7f447 to
900e66d
Compare
tonistiigi
approved these changes
Feb 9, 2024
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.
related to https://github.com/tonistiigi/binfmt/actions/runs/7842729670/job/21403764984#step:10:32
since #158, provenance is created by default with bake action v4. Fix the issue by disabling platform split behavior for the output.
Will look like this:
As provenance is for both binfmt and qemu bins I think the name is fine or maybe you would want a provenance attached to each binary so deidcated stage in dockerfile?