fix(79368): Fix a Bug when generating SBOM for container images using… #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… absolute / Relative path
What this does
There is bug on snyk container SBOM. When the SBOM is generated on docker-archives, The scan fails with error
error while invoking depgraph workflow: could not parse container name: invalid reference formatWe created a support ticket with SNyk with request ID 79368.
This PR tries to fix the said bug to allow SBOM generation on archive files with absolute / relative path.
Explain why this PR exists
container-cli/internal/workflows/sbom/depgraph.go
Line 29 in 6d9b948
Notes for the reviewer
I haven't tested this. Since I can't find the contribution guide or how to build or test this repo. Please feel free to contribute to this PR. Or feedback whats needed from me.
Instructions on how to run this locally, background context, what to review, questions…