-
Notifications
You must be signed in to change notification settings - Fork 598
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
syft is unable to locate image locally in k8s with containerd runtime #1048
Comments
Based on my understanding of syft, anchore/stereoscope needs to support this. |
Thanks for filing the issue @ibreakthecloud! We'll take a look when we have some time and talk about what it would take to support pulling from the local containerd runtime rather than having syft fall back to the registry each time |
Hey @ibreakthecloud! We're going to close this issue and follow the support for when we get the change merged in anchore/stereoscope#67 |
we have the same issue. we would like to create SBOM from inside container/pod using syft and get image from containerd deamon. But when we use Is this resolved ? |
@mabilgen I dont' think so, see in stereoscope pullImageIfMissing . . I think the docker.io is prefixed before checking local daemon |
What happened:
Running
syft
inside pod running in k8s with underlying containerd runtime always falls back to cloud registry.I have a k8s cluster(containerd), with an application pod(image is on quay private repo) and a syft pod, syft pod has two sock path mounted(docker and containerd).
Running syft inside syft pod with quay private image fails, because it looks up image in quay registry although it is present locally.
application image is present locally
What you expected to happen:
Look for image locally before falling back to registry in case of containerd
How to reproduce it (as minimally and precisely as possible):
Try scanning any image from pricate repo present in k8s cluster with containerd runtime
Anything else we need to know?:
Also, running syft inside pod in containerd k8s fails for few image but passes if ran on same image on ubuntu machine or mac
example:
failure inside pod
success on vm(ubuntu):
Environment:
syft version
:cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: