-
Notifications
You must be signed in to change notification settings - Fork 521
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
Redis not listed in the artifact lists of the bitnami/redis image #2764
Comments
I think this is because the binary classifier for redis matches against the amd64 build of redis but _not_the arm64 build. ❯ syft -q --platform=linux/amd64 docker.io/bitnami/redis@sha256:c1843bcdb2f413d2aff67adbaf482082673cd40ec602fa9fefad74ec685cb813 | grep -i ^redis
redis 7.2.4 binary
❯ syft -q --platform=linux/arm64 docker.io/bitnami/redis@sha256:c1843bcdb2f413d2aff67adbaf482082673cd40ec602fa9fefad74ec685cb813 | grep -i ^redis I believe the digest points to a multi-architecture manifest, so when syft asks docker to pull the image, the client decides which platform to pull, and if the client pulls the linux/amd64 platform, redis is found, but not if it pulls the linux/arm64 platform. I'll leave this issue open as a request to enhance the binary classifier to detect the arm64 build of redis. |
Please let me report additional not listed cases. syft does not detect redis frmo 3/8 OS/ARCH of redis:latest.
format includes text - buildkitsandbox
bitnami
|
What happened:
I am creating an SBOM for the
docker.io/bitnami/redis
image.As I was looking at the artifacts, I noticed that the redis binary was absent from the list of artifacts in the SBOM.
bitnami/redis SBOM syft-1.1.1
What you expected to happen:
The redis binary should be listed as an artifact in the SBOM
Steps to reproduce the issue:
Anything else we need to know?:
I compared the SBOM with syft version
0.101.1
and the only difference is that in the older version there is a mention of the redis in the list of artifacts:bitnami/redis SBOM syft-0.101.1
Environment:
syft version
:cat /etc/os-release
or similar):macos
,m1
The text was updated successfully, but these errors were encountered: