Open tomgeorge opened 1 year ago
I would also hazard a guess that this affects any golang
container. We are instructing teams to not have their runtime containers be FROM golang
, but I think xray should know enough to not scan test data.
Hi @tomgeorge, Thanks for reporting this issue. Our apologies for the inconvenience caused by this. The above issue is already resolved on JFrog Xray side and will be released soon. ( I believe that it will be Xray version 3.71.X and higher) I will update here once it's released.
Describe the bug
Running
jf docker scan
on a container image based ongolang:1.20.1-alpine3.17
fails when trying to indexpax-bad-hdr-large.tar.bz2
which is in the container at/usr/local/go/src/archive/tar/testdata/pax-bad-hdr-large.tar.bz2
.Current behavior
Reproduction steps
docker build -t golang-test .
jf docker scan golang-test
Expected behavior
I expect it to not fail on this piece of test data, or to skip it like many of the
invalid tar header
errors.JFrog CLI version
2.35.0
Operating system type and version
Mac/Linux, happens locally and in CI
JFrog Artifactory version
7.55.9
JFrog Xray version
3.69.3