-
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 hangs for v1.12.3 cluster, cannot find ionice in path. #3386
Comments
I tried to recreate from the master branch with v1.12.3 and virtualbox, but it ran properly. I did see the following errors, however: Dec 04 05:54:33 minikube kubelet[2739]: E1204 05:54:33.631346 2739 fsHandler.go:121] failed to collect filesystem stats - rootDiskErr: failed to exec du - exec: "ionice": executable file not found in $PATH, rootInodeErr: failed to exec cmd [ionice -c3 nice -n 19 find /var/lib/docker/overlay2/aef75bb7ea5876aa4f0be828e6d3ae84718499f3856ed1e0ed50d65229932c02/diff -xdev -printf .] - exec: "ionice": executable file not found in $PATH; stderr: , extraDiskErr: failed to exec du - exec: "ionice": executable file not found in $PATH |
Plenty of them: $ sudo journalctl | grep ionice | wc -l
2518 |
Thanks for looking into it! I built from |
Whoops---turns out this is still an issue on $ minikube start --kubernetes-version=v1.12.3 --cpus=4 --memory=4096 --vm-driver=vmwarefusion
$ minikube stop
$ minikube start This caused the hang on "Starting cluster components..." that I described above. The strange thing is that this sequence of commands worked just fine: $ minikube start --kubernetes-version=v1.12.3 --cpus=4 --memory=4096 --vm-driver=vmwarefusion
$ minikube stop
$ minikube start --kubernetes-version=v1.12.3 --cpus=4 --memory=4096 --vm-driver=vmwarefusion I imagine one of the four flags has to be specified explicitly on each start, rather than being inferred from the VM's previous state. A little guesswork and testing suggests that it might be |
There is ionice in the latest release! $ which ionice
/bin/ionice |
Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug Report
Environment:
minikube version
): v0.30.0cat ~/.minikube/machines/minikube/config.json | grep DriverName
):vmwarefusion
cat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
): v0.30.0brew cask install minikube
What happened:
Running
minikube start --kubernetes-version=v1.12.3 --vm-driver=vmwarefusion
followed byminikube stop
followed byminikube start
again causes minikube to hang forever on "Starting cluster components...," while the VM logs errors that it cannot findionice
in itsPATH
.What you expected to happen:
The second
start
command should have brought up the minikube VM successfully.How to reproduce it (as minimally and precisely as possible):
Start, stop, and attempt to restart a cluster with K8S 1.12.3 and/or the VMWare Fusion driver.
Output of
minikube logs
(if applicable):Anything else do we need to know:
Thanks in advance for any guidance you can provide! ✨
The text was updated successfully, but these errors were encountered: