feat: container scan support for cgo and stripped Go binaries #6353
+21
−8
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.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
Upgrades snyk-docker-plugin to add support for detecting CGO-linked and stripped Go binaries in container images. Previously, these binaries could not be analyzed for dependencies. With this update, snyk container will identify and report on Go applications compiled with CGO or built with stripped symbols.
Where should the reviewer start?
How should this be manually tested?
Run snyk container test against a container image containing a CGO-compiled or stripped Go binary and verify the binary is detected and analyzed. Here is an example of scanning
docker.elastic.co/beats/filebeat:8.11.0public image:Without this change, we detect only the base image vulnerabilities:
What's the product update that needs to be communicated to CLI users?
Snyk Container now supports detection of CGO and stripped Go binaries, improving vulnerability coverage for Go applications in container images.