minikube: cache with quay.io issues: Docker-Content-Digest and 405 Method Not Allowed

Hello,

With minikube 1.0.0 on windows, I am not able to cache images from quay.io docker repository.

$ minikube cache add quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0
2019/03/28 14:30:05 No matching credentials were found, falling back on anonymous

!   Failed to cache and load images: caching images: caching image C:\Programs\Cygwin\home\cvila\.minikube\cache\images\quay.io\kubernetes-ingress-controller\nginx-ingress-controller_0.23.0: manifest digest: "sha256:603b7018c941b1117da4eb980c8043992ad37abdde3636fcbae1f34bcfff443f" does not match Docker-Content-Digest: "sha256:e1292564ba5f1fd75005a4575778523d3309fb5d5d57f6597234c0b1567641f6" for "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0"

*   Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
-   https://github.com/kubernetes/minikube/issues/new

From what I understood, it comes from https://github.com/google/go-containerregistry/issues/119, which has been recently fixed (beg March) by https://github.com/google/go-containerregistry/pull/387. Maybe we just need to make sure we compile minikube with the latest release of go-containerregistry ?

Side question, is there a way to avoid the No matching credentials were found, falling back on anonymous, when we put in cache a public image (which does not require any credentials to be passed)

Thanks !

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 2
Comments: 19 (9 by maintainers)

Most upvoted comments

➜  ~ minikube cache add quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0


E1009 13:42:20.927214   47862 cache_images.go:79] CacheImage quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 -> /Users/reegnz/.minikube/cache/images/quay.io/kubernetes-ingress-controller/nginx-ingress-controller_0.23.0 failed: manifest digest: "sha256:603b7018c941b1117da4eb980c8043992ad37abdde3636fcbae1f34bcfff443f" does not match Docker-Content-Digest: "sha256:e1292564ba5f1fd75005a4575778523d3309fb5d5d57f6597234c0b1567641f6" for "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0"

💣  Failed to cache and load images: caching images: caching image /Users/reegnz/.minikube/cache/images/quay.io/kubernetes-ingress-controller/nginx-ingress-controller_0.23.0: manifest digest: "sha256:603b7018c941b1117da4eb980c8043992ad37abdde3636fcbae1f34bcfff443f" does not match Docker-Content-Digest: "sha256:e1292564ba5f1fd75005a4575778523d3309fb5d5d57f6597234c0b1567641f6" for "quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0"

😿  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉  https://github.com/kubernetes/minikube/issues/new/choose
➜  ~ minikube version
minikube version: v1.4.0
commit: 7969c25a98a018b94ea87d949350f3271e9d64b6

Doesn’t look fixed to me. Although now we only have a the Content-Digest issue. (I am running the MacOS version).

Should I open a new issue about that? Still only affects the quay.io images.

reegnz on Oct 9, 2019

This was fixed in minikube v1.4:

minikube cache add quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0

tstromberg on Sep 20, 2019