-
Notifications
You must be signed in to change notification settings - Fork 605
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 at 'Cataloged contents' #3068
Comments
Thanks for the issue @jc776 Just a couple of points. Are you able to run syft in verbose mode? This will capture the output while it's running. Either You mentioned that older versions worked. To confirm this, if required, you should be able to grab any old binary version of syft to compare the run/output.
|
Process in
|
Thanks. I'm not surprised by the CPU usage, as it looks like we're arriving here where some (a lot) of digests are (attempting to be) calculated, and failing. Does it produce sane output if you omit generating an |
Syft 1.9 does complete successfully when producing standard output:
Syft 1.3 does complete successfully producing the
|
What happened:
I'm using syft to scan all directories on an EC2 instance for an SBOM.
It hangs at this point, it's using 100% CPU, but never completes:
The output file remains empty:
Similar command completed OK and writes the sbom file in previous syft version 1.3.0
Similar command stuck without completing in previous syft versions 1.4.1 and 1.8.0, but I don't have saved output from those ones.
Running the same scan via
grype
does complete and does the vulnerability scan step correctly, but isn't set to output an sbom file.What you expected to happen:
Command completes and writes
sbom-full.spdx.json
.Steps to reproduce the issue:
Not sure - using this command:
Anything else we need to know?:
Environment:
syft version
:cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: