-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
SBOM. sbom flags are not respected #23915
Comments
@AndreiPaulau thanks for the report. Could you please update the @l0rd PTAL in case this is wsl / k8s related. |
@lsm5 Updated with command output |
It looks like in podman we are not parsing sbom command line arguments and that's done buildah CLI side. Should not be related to WSL or Kube. |
@AndreiPaulau would you like to submit a PR to fix this? |
@l0rd Unfortunately, don't have much experience in Go |
…rguments Signed-off-by: Alex Guidi <[email protected]>
…rguments Signed-off-by: Alex Guidi <[email protected]>
…rguments Signed-off-by: Alex Guidi <[email protected]>
…rguments Signed-off-by: Alex Guidi <[email protected]>
Issue Description
SBOM flags are not respected while
podman build
command.Meanwhile sbom options fails if wrong input.
Builds were made inside
container quay.io/containers/podman:v5
Checked over tags 5.0 - 5.2
At the same time buildah build command works as expected.
Steps to reproduce the issue
podman build:
Dockerfile
Describe the results you received
Simply skipped scanning and further SBOM file creation
While building with buildah: pulled trivy -> scanned image -> create layer with /app/sbom-spdx.json file
buildah build with the same options:
Describe the results you expected
Describe the results you expected
podman info output
Podman in a container
Yes
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: