-
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
Minikube start does not work. #19110
Comments
I am in the same boat. Followed the suggested issues and still unable to start mini-kube. |
Hi @romu42, thanks for reporting your issue with minikube. We have seen this occasionally but have so far been unable to reproduce this ourselves. The current theory is that the After you attempt to start minikube and it fails, could you run |
ran
|
Interesting, so the binaries are there, and that correlates to your logs:
And immediately after that the kubectl service is started:
Which fails due to the binaries not being present:
So I'm not sure how they can be there but not be there at the same time, my current guess is maybe something is wrong with the preload side of things, if you do a delete and then try starting with |
I tried that. Seems to still be a problem. Just a side note: I installed
I think it is a little odd that it is Uname returns
I am not sure if it is significant or not, or if that is the way it should be? |
That's not good... I can see everything with your setup is
So it should be using an arm64 kicbase image, but This is why you're getting The question now is why is Docker pulling the amd64 version of the kicbase image instead of arm64? Have you configured Docker Desktop at all? Any experimental settings enabled? To see if this is a Docker Desktop issue could you try the following:
If you get When minikube pulls the image it specifically sets the platform based on the binary arch, so it should pull the arm64 image regardless unless something in Docker is overriding this.
I see you ran Just to make sure we get rid of all possible causes could you run I created a PR (#19205) to check the arch of the kicbase image on start and will redownload if the arch doesn't match. I can provide the binary from the PR once its built if you want to test that as well. |
Here's an arm64 macOS binary with the kicbase arch check if you want to download it and try it after trying the above steps. https://storage.googleapis.com/minikube-builds/19205/minikube-darwin-arm64 |
This could have been entirely my fault. I had an export in my shell that set: To quiet I removed the export and retested and it is now working as expected. Minikube pulls one image ( 648c6affc8e4 ) which is arm64
With
one (648c6affc8e4) is arm64 and one (5a6e59a9bdc0) is amd64. Sorry for the slow turn-around time. Hope this helps and if there is anything more I can do please let me know. Thank you for your time and assistance. |
What Happened?
Minikube will not start despite multiple attempts.
[ERROR KubeletVersion]: couldn't get kubelet version: cannot execute 'kubelet --version': executable file not found in $PATH
I have tested the recommendations in:
#18939
and
#18884
without success.
Attach the log file
logs.txt
Operating System
macOS (Default)
Driver
Docker
The text was updated successfully, but these errors were encountered: