-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
E0629 Error caching images for kubeadm fetching remote image UNAUTHORIZED Not Authorized. #4643
Comments
I am curious, are you in a network that restricts your access to docker hub? |
My local docker can pull images just fine. Note I have login with "credsStore": "pass" which works correctly.
|
seems like you are trying to pull an image from a private regsitery ? 1- first connect to minikube's docker |
I figured out what was happening. During the first run minikube downloads files from docker under the ~/.minikube/cache directory. If you have your local docker configured with interactive authentication the prompt for authentication is not exposed so you wind with with an authentication failure. Simply removing the line '"credsStore": "pass"' from the .docker/config.json allowed minikube to bootstrap itself correctly. So the issue with minikube seems to be that it does not interact correctly with docker credential managers (e.g. credsStore) when the credential manager requires user feedback. |
@flstaats Thank you so much for sharing for this work around you found , we totally need to provide a better solution message ! we should detect this and advice user to do the workarround you did ! I would be happy to review any PR that addresses this isssue ! |
I kept getting minikube the error "invoking docker-credential-desktop: exit status 1; output: No stored credential for https://gcr.io" and the Minikube cluster kept timing out on start. My |
I believe this was fixed in #5224 - and is available to test in the v1.4 betas. |
minikube v1.4 was released, which addresses this. |
I have validated that minikube v1.4 bootstraps a new k8s environment with my ~/.docker/config.json having the value "credsStore": "pass" set. Thanks for fixing this inconvenience! |
Getting error message on
minikube start
that caching images for kubeadm is failing. Not clear from the logs or documentation on how to resolve. On an open internet connection in the United States. Fresh install of minikube and the started k8s cluster seems to run correctly even with the caching issue. Using -v 7 log level did not appear to provide additional information regarding the caching.E0629 07:57:04.266903 11077 start.go:403] Error caching images: Caching images for kubeadm: caching images: caching image /home/flstaats/.minikube/cache/images/k8s.gcr.io/k8s-dns-dnsmasq-nanny-amd64_1.14.13: fetching remote image: UNAUTHORIZED: Not Authorized.
Verified that no files are actually cached after command is run:
The exact command to reproduce the issue:
$ minikube start
# Configured to use the kvm2 driver by defaultThe full output of the command that failed:
The output of the
minikube logs
command:minikube logs
% uname -a # Note: dell xps 13 9380 developer edition with full apt-get dist-upgrade
Linux fls 4.15.0-1043-oem #48-Ubuntu SMP Fri Jun 14 09:57:55 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: