-
Notifications
You must be signed in to change notification settings - Fork 867
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: disable docker sbom and attestations #2528
Conversation
@zachaller Not sure how far back you want to cherry pick this. |
Signed-off-by: Justin Marquis <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
Codecov ReportBase: 81.69% // Head: 81.69% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #2528 +/- ##
=======================================
Coverage 81.69% 81.69%
=======================================
Files 126 126
Lines 19136 19136
=======================================
Hits 15634 15634
Misses 2709 2709
Partials 793 793 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Signed-off-by: Justin Marquis <[email protected]> Signed-off-by: Justin Marquis <[email protected]> Signed-off-by: zachaller <[email protected]>
Signed-off-by: Justin Marquis <[email protected]> Signed-off-by: Justin Marquis <[email protected]>
Signed-off-by: Justin Marquis [email protected]
The newer BuildKit v0.11 now enables a provenance attestation by default. These attestations are stored as a manifest object of
unknown on unknown
attached to the root image index object."To prevent container runtimes from accidentally pulling or running the image described in the manifest, the platform property of the attestation manifest will be set to unknown/unknown"
This prevents our current Sbom generation from working properly.This PR is a workaround by disabling attestations and sboms by default. These new inputs for the
docker build and push action
require the newer version of build and push.Note: I have tested this workaround locally.