-
Notifications
You must be signed in to change notification settings - Fork 279
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
Feature: Retrieve SBoM from Registry for Remote Images #2020
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2020 +/- ##
=======================================
Coverage 79.52% 79.52%
=======================================
Files 174 174
Lines 13077 13077
=======================================
Hits 10398 10398
Misses 2016 2016
Partials 663 663
Flags with carried forward coverage won't be shown. Click here to find out more. |
@natalieparellano pls, review this pr !! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Thank you for the PR @sarthaksarthak9 🙏🏼
I think you need to fix the DCO - can you sign-off your second commit?
srry for this :) |
Signed-off-by: sarthak <sarthaknegi908@gmail.com>
Summary
when attempting to download a (SBoM) from a remote image that is not present in the Docker daemon, the pack tool throws an error, forcing the user to download the image to the daemon before extracting SBoM information.
Output
Before
After
Documentation
Related
Resolves #1615