This repository has been archived by the owner on Nov 29, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 44
Linux docker scan not working for locally built/cache image #151
Comments
Grabbed a container inspect of the snyk container:
|
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Description
On Ubuntu VM (tested on both 20.04.1 and 18.04.5) docker scan is erroring trying to scan an image I built locally with the following:
Steps to reproduce the issue:
docker scan [image]
Describe the results you received:
Getting the error shown above
Describe the results you expected:
Snyk scan results
Additional information you deem important (e.g. issue happens only occasionally):
Have done a
docker scan --login
successfully previously.Also have tried with or without having done a
docker login
Output of
docker version
:Output of
docker scan --version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
VirtualBox as defined in https://github.com/ericsmalling/vagrantfiles/blob/main/docker-ce/Vagrantfile
Also seeing the same behavior on an AWS Cloud9 instance running on Ubuntu 18.04.5 instance.
The text was updated successfully, but these errors were encountered: