-
Notifications
You must be signed in to change notification settings - Fork 593
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 failed to parse Singularity image #1150
Comments
Hi @saromleang, thanks for the report, and sorry for the delay responding! We are fairly backed up right now but we will take a look at your issue as soon as we can, and let you know if we need more information. Thanks again for your patience. |
Thanks for the detail in the bug report @saromleang ! @tgerla I'm happy to take a look at this if it helps. Looks related to anchore/stereoscope#125. |
@tri-adam thanks for the ping, and for the patches! @saromleang, Singularity support has been added to Syft as of version 0.53.1. I'll go ahead and close this issue, but if you have any more trouble just let us know. Thanks! |
Hi @saromleang, sorry, I am re-opening this issue because I noticed you reported this issue with Syft version 0.53.4. Can you please try the latest version, and maybe @tri-adam has some suggestions? |
I'm able to reproduce the issue described, even with the latest versions of SingularityCE and Syft, specifically: $ singularity --version
singularity-ce version 3.10.2
$ syft --version
syft 0.54.0 The exact error I'm getting is the same as @saromleang reported:
Haven't figured out the root cause of this yet. Will report back when I know more! |
@tri-adam could it have something to do with the path being parsed? I notice that in the error message the path is missing a forward-slash before opt:
|
@saromleang that's expected, as the At this point, I am fairly confident the bug is with reading inodes that reference a fragment block within the SquashFS filesystem. I'll report back once I've researched the issue further and (hopefully) have a fix ready to go for the appropriate repo(s). Thanks for your patience! |
Just to update with the latest, the underlying cause is described in CalebQ42/squashfs#14. A patch for that is now available. anchore/stereoscope#141 has patched the issue in |
Closing this with the fix now being in the latest release! If anyone still has an issue just comment here and I can reopen. |
What happened:
When running syft on a Singularity image containing an installation of Intel OneAPI the following error is encountered:
What you expected to happen:
I expected syft to parse the image and catalog the packages within the image.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
This is encountered even when Intel OneAPI is installed manually in a Singularity container or installed through the package manager in a Singularity container. The reproducer above uses the official Intel OneAPI image from DockerHub.
However, taking the same approach but using Docker instead of Singularity, syft is able to load and parse the image and catalog the 680 packages.
Environment:
syft version
:0.53.4
cat /etc/os-release
or similar):singularity --version
:singularity version 3.7.1-1
The text was updated successfully, but these errors were encountered: