-
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
Unable to load cached images #15237
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Comments
spowelljr
added
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
labels
Oct 28, 2022
Just got it to fail!
So the preload download/untar is failing, investigating further. |
It seems the download is failing
|
It wasn't downloaded on this start, and the previous start was fine, so between the previous start and delete the contents of the preload was wiped. I may have ctrl+C the previous run, can't remember, but might be part of the puzzle. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Occasionally when starting minikube I see the error:
❌ Unable to load cached images: loading cached images: stat /Users/powellsteven/.minikube/cache/images/arm64/registry.k8s.io/kube-controller-manager_v1.25.3: no such file or directory
I have two ideas of what's happening
docker images
fails as docker may not have finished restartingI've unfortunately not saved the logs and the failure is very flakey and haven't been able to reproduce it. So if anyone runs into this please run
minikube logs --file=logs.txt
and upload your logs.Possibility of
docker images
failingminikube/pkg/minikube/bootstrapper/kubeadm/kubeadm.go
Lines 922 to 930 in 074e681
minikube/pkg/minikube/cruntime/docker.go
Lines 597 to 612 in 074e681
When starting the cluster the preload is downloaded and then try to load cached images. At the end of the preload step docker is restarted. During the load cached images step
docker images
is ran and then we check if all the expected images are present. If thedocker images
command fails we returnfalse
and try loading images from cache but most people don't have images cached as they're using preloads, which is what causes the error being printed. An improvement we can do here is log the failure ordocker images
instead of just returningfalse
.If we have a log file we can confirm this by the absence of
Got preloaded images
in the logs which would indicate thedocker images
command failed.Possibility of preload failing
minikube/pkg/minikube/bootstrapper/kubeadm/kubeadm.go
Lines 922 to 924 in 074e681
minikube/pkg/minikube/cruntime/docker.go
Lines 614 to 619 in 074e681
It's possible that the preload download and untarring is failing. If the preload step fails we don't stop execution, we just log it as info, then starting the loading from cache step. If the tar failed there will be no images present and the log
Got preloaded images
should be empty along with multiple%s wasn't preloaded
.The text was updated successfully, but these errors were encountered: