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
What would you like to be added:
Currently syft & grype look for certain locations for finding the container images. It works fine if the container image is built either via docker or podman as the images they build reside in certain locations and those are part of the supported sources here.
Images built using buildah though reside in different location (usually containers-storage) and when scanning using syft, it scans the remote image instead of the locally built image.
Why is this needed:
Need to add support for scanning images built using non-daemonize tool like buildah. Add a new source where syft can look for when scanning image locally before checking OciRegistry.
Additional context:
The text was updated successfully, but these errors were encountered:
wagoodman
changed the title
Support for scanning images built using buildah
Add support for containers-storage backend for container images
Dec 7, 2023
What would you like to be added:
Currently syft & grype look for certain locations for finding the container images. It works fine if the container image is built either via
docker
orpodman
as the images they build reside in certain locations and those are part of the supported sources here.Images built using buildah though reside in different location (usually
containers-storage
) and when scanning using syft, it scans the remote image instead of the locally built image.Why is this needed:
Need to add support for scanning images built using non-daemonize tool like
buildah
. Add a new source where syft can look for when scanning image locally before checking OciRegistry.Additional context:
The text was updated successfully, but these errors were encountered: