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 stuck on some images (also affecting grype) #764
Comments
Thanks for the report @tsunamaru -- I've reproduced the bug. I suspect an issue with the terminal UI causes some race condition; more investigation is necessary to figure it out. |
Thanks for investigation and provided workaround @jonasagx. |
Related: #733
|
A PR from stereoscope mistakenly closed this ticket. |
Update version of stereoscope with a fix for anchore#549 and is related to a Syft issue: anchore/syft#764 Signed-off-by: Jonas Galvão Xavier <jonas.agx@gmail.com>
@tsunamaru if you're curious: |
Thanks for swift action @jonasagx. I used grype and syft tools to bulk extract log4j versions from docker images on company Nexus. From ~30k images there was ~500 which caused grype/syft stuck (though all those images were somewhat old -- built in 2018-2019). Anyway grype and syft tools saved me tremendous amount of time, so thank you (anchore people and contributors) for making it! |
What happened:
On some images syft (and grype) infinity showing "Loading image" - "Saving image to disk" and not responding to SIGINT/SIGTERM.
What you expected to happen:
Scan to be done.
How to reproduce it (as minimally and precisely as possible):
I can send you example image by any private means (it contains company private code and thus can't be uploaded to public share or registry, sorry). Ideally, if you give me some email for contact.Just execute
syft noway13/ldap-passwd-webui:latest
.Anything else we need to know?:
Initially reported in anchore/grype#549
Environment:
syft version
:cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: