minikube: Running `minikube delete` breaks `minikube start`
Deleting a running cluster seemed to break minikube.
[~]$ minikube start --show-libmachine-logs=true --stderrthreshold=0
Starting local Kubernetes cluster...
I0707 11:41:38.472798 13936 cluster.go:60] Machine exists!
I0707 11:41:38.730192 13936 cluster.go:60] Machine exists!
I0707 11:41:38.784298 13936 cluster.go:60] Machine exists!
E0707 11:41:38.849506 13936 start.go:70] Error starting host: Error getting state for host: machine does not exist
Removing the local state (~/.minikube/) fixed the issue in my local environment (OS X + Virtualbox).
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 7
- Comments: 15 (2 by maintainers)
Hey, until we track down and fix the issue you can just run: minikube delete rm -rf ~/.minikube
Then start
Just FYI - you can get this error message (putting here for SEO purposes):
in my case, using
vm-driver xyhyve- had tosudo rm -rf ~/.minikubeas some files root owned. Installed from cask, minikube version - 0.23.0.Hitting this in OSX 10.12.6, minikube version v0.22.3, installed via homebrew cask, with virtualbox 5.1.12r112440
minikube deletecauses machine doesn’t exist errors on subsequentminikube startcalls.rm -rf ~/.minikubesolves the problemIt turned out the culprit was the
Security & Privacysetting inmacOSpreventedVirtualBoxfrom installed properly. This worked for me:virtualboxby trash it && delete all virtualbox related files/folder under~/Library/allowbutton in theSecurity & Privacy.minikube deleterm -rf ~/.minikubeminikube start--> it should downloadGood luck!
I just had this problem with minikube 0.26.1. Looking at the verbose output, it hangs on:
@aaron-prindle Might be worth re-opening this one.
Same issue on OSX Sierra + virtualbox. It seems I always have to delete the ~/.minikube directory after stopping minikube. It will then redownload the latest iso and start again
Got this on v0.14 on a osx/xhyve.