You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please add support for scanning docker image which is present locally (just built) instead of pulling it from the registry.
Preferred Solution
If the image is available locally, don't reach the registry, and do that only if it's absent. Or implement additional flag like --image-priority local | --image-priority remote to control the behaviour.
Additional Context
I as a user want to prevent situation when image was pushed to the registry with leaked secret(s)/vulnerabilities.
The text was updated successfully, but these errors were encountered:
Hi there!
Thank you for taking the time to open this issue, we really appreciate your contribution to the project!
We’ll take a look and get back to you as soon as we can. If we need any clarification, we’ll follow up here.
In the meantime, feel free to share any additional context or examples that might help us understand the issue better.
Thanks again for helping make this project better!
Description
Please add support for scanning docker image which is present locally (just built) instead of pulling it from the registry.
Preferred Solution
If the image is available locally, don't reach the registry, and do that only if it's absent. Or implement additional flag like
--image-priority local
|--image-priority remote
to control the behaviour.Additional Context
I as a user want to prevent situation when image was pushed to the registry with leaked secret(s)/vulnerabilities.
The text was updated successfully, but these errors were encountered: