-
-
Notifications
You must be signed in to change notification settings - Fork 177
SBOM generation issue cdxgen binary #1673
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
Comments
@hnaung Could you investigate with a colleague and triage this further? Issues are only for reporting bugs that can be reproduced. |
Hi @prabhu, Thanks for your response. I did some further investigation and noticed a key difference: When running However, when running the standalone cdxgen binary directly, it doesn't produce the expected SBOM output for all the vendor binaries such as "sbom-tool-linux-64", "cycloneDX-cli" and etc. All the vendor binaries SBOM generation is working as expected in cdxgen container server.
Standalone
Both tests were performed on RHEL9 machine. Thank you for your input and insights on this! Looking forward to any further thoughts or guidance. |
Greetings!
I used cdxgen binary and cdxgen container to generate SBOM for vendor-binaries. It works partially, especially for "jar" files but other binaries are not working at all.
However, when I setup cdxgen as a container server and generate SBOM inside that cdxgen container server, it does works for "jar" files as well as other binaries. Any suggestions or insights would be highly appreciated.
The text was updated successfully, but these errors were encountered: