Skip to content
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 fallback generation #13

Open
jedevc opened this issue Jan 19, 2023 · 1 comment
Open

SBOM fallback generation #13

jedevc opened this issue Jan 19, 2023 · 1 comment

Comments

@jedevc
Copy link
Contributor

jedevc commented Jan 19, 2023

Not every image will have SBOMs attached to it (especially as it requires opt-in).

If an SBOM is requested, but one is not attached, we should attempt to create a scan of the image using one of the buildkit scanners as a fallback. This allows consumers of the library to more transparently consume SBOM results, and easily query it - this could be massively useful for the docker sbom command and similar.

We should probably only enable this behavior if there's some user-specified config to do this, so we should have a global config object for the loader that allows configuration of this behavior.

@tonistiigi
Copy link
Member

  1. Make sure the library doesn't run these things locally. This is not safe. To use this user would need to provide docker or buildkit endpoint.
  2. This should be opt-in. It has very different performance characteristics than just reading the SBOM from the registry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants