-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't pull fsLayers with public GCR image #83
Labels
Comments
GCR supports only docker manifest V1, we somehow dropped support of V1, I've fixed this regression, sending a patch. Here is the reason: |
Merged
hashmap
pushed a commit
that referenced
this issue
Mar 12, 2018
hashmap
added a commit
that referenced
this issue
Mar 12, 2018
Fixed in 2.0.2 |
Awesome, thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've deployed Clair into a Kubernetes cluster from the released quay.io/coreos/clair:v2.0.1 Docker image. I'm trying to use Klar 2.0.1 to scan a public image hosted on
gcr.io
, Google's container registry. But when I do that, I'm getting theCan't pull fsLayers
error:Here's the command I'm running:
I get this error for any public
gcr.io
image, while images hosted elsewhere scan just fine. Note that I'm not running any of this on GCP and I'm not using a private image, so I'm not authenticating with the instructions here: https://github.com/optiopay/klar#google-gcr-supportThe text was updated successfully, but these errors were encountered: