-
Notifications
You must be signed in to change notification settings - Fork 534
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bumps the version of the docker-plugin to support trimmed, stripped and Cgo binaries. See [snyk-docker-plugin #447](snyk/snyk-docker-plugin#447) for more info.
- Loading branch information
1 parent
b46e07b
commit 47af5ca
Showing
2 changed files
with
8 additions
and
8 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
47af5ca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @tommyknows, is there a way to disable or ignore the Go binary scan when doing a snyk container test?
When I am running a snyk container test, I am getting a 'no pcln table found in Go binary' error when scanning containers installed with the 'docker-ce'cli' or the 'mongodb-database-tools' apt packages. I want to keep the snyk scan of course but these packages are mandatory for my use-case, so I need to keep them whilst also having my pipeline succeed.
47af5ca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @aneqinun, sorry for breaking your use case. That there are Go binaries without PCLN tables was something we were not aware of until yesterday, when we noticed this breaking as well. We have just pushed a change that will skip Go binaries without a PCLN table, which means you can simply update your CLI to 1.1005.0 and it should work again.
47af5ca
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @tommyknows, no worries. Thanks very much for the rapid response, all of my issues now seem to be resolved with the new v1.1005.0 as you said.
Much appreciated!