google/kctf

Docker Snyk messages break kCTF parsing

arxenix opened this issue · 2 comments

test/kctf_test/testchal
▶ kCTF[ctf=kctf_test,config=local-cluster,chal=testchal] > make -C challenge
make: Entering directory '/home/arx/ctf/test/kctf_test/testchal/challenge'
cc     chal.c   -o chal
make: Leaving directory '/home/arx/ctf/test/kctf_test/testchal/challenge'

test/kctf_test/testchal
▶ kCTF[ctf=kctf_test,config=local-cluster,chal=testchal] > kctf chal start
[*] building image in "/home/arx/ctf/test/kctf_test/testchal/challenge"
[*] Image ID "5bd50bd642bd38fd43fa265c0cb5259daae60de68c78aa3211a7fcf04fc12157

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them"
[*] building image in "/home/arx/ctf/test/kctf_test/testchal/healthcheck"
[*] Image ID "23cf15ad4349a24d755b7cf17750578f4a487acfcc70969194394c8e3ed22381

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them"
Error parsing reference: "5bd50bd642bd38fd43fa265c0cb5259daae60de68c78aa3211a7fcf04fc12157\n\nUse 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them" is not a valid repository/tag: invalid reference format: repository name must be lowercase

newer versions of docker spit out a Snyk message at the end of docker build -q {container}. kCTF is currently parsing it as part of the container ID.

this can be fixed on the user's end by setting the environment variable DOCKER_SCAN_SUGGEST=false, but kCTF may want to fix the parsing so that it works by default.

Looks like this was fixed upstream, so newer versions should stop doing this:
docker-archive/compose-cli#1517

ah, my bad. thanks!