minikube: hyperv: "minikube stop" fails (Shutting down 0% until it eventually times out)
BUG REPORT Please provide the following details:
Environment: Windows 10 Pro 1803
Minikube version (use minikube version): v0.28.0
- OS (e.g. from /etc/os-release): Windows 10 Pro 1803
- VM Driver (e.g.
cat ~/.minikube/machines/minikube/config.json | grep DriverName): Hyper-v - ISO version (e.g.
cat ~/.minikube/machines/minikube/config.json | grep -i ISOorminikube ssh cat /etc/VERSION): v0.28.0 - Install tools:
- Others:
What happened: Minikube stop fails to stop minikube VM
What you expected to happen: VM stops
How to reproduce it (as minimally and precisely as possible): With running minikube, perform minikube stop
Output of minikube logs (if applicable):
Anything else do we need to know:
Clean install of Minikube 0.28.0 (deleted .minikube folder)
Command sits with powershell overlay showing Shutting down 0% until it eventually times out
Trying to shutdown via Hyper-V manager/Powershell doesn’t work either
Opening VM in hyper-v shows command prompt - may not be relevant?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 49
- Comments: 52 (18 by maintainers)
Quite annoying indeed. I’ve found
to be the fastest workaround.
You can combine the commands to issue a shutdown in one line:
minikube ssh "sudo poweroff"Same environment and same problem here. Also, if I try to stop minikube from Hyper-V Manager I get the following error:
Still happening here as well…
OS: Windows 10 Pro (17134) VM-Driver: HyperV Minikube: v.0.31.0 (just updated a couple of days again)
Using
minikube sshto do a shutdown is getting pretty old… Any chance of a fix for the new year?Is there an update to this issue?
Experienced this with
minikube version: v0.32.0Thanks for the
minikube ssh | sudo poweroffworkaround for this issue - even telling Hyper-V to shut the device down did not work (Presumably because it was in a frozen // not responding state).Is there any further information those of us who have this problem can provide to assist in resolving? I’ve not seen anything particularly nasty in the event logs or similar…
Edit I have noticed that the
sudo shutdownin minikube 0.27.0 does an immediate shutdown, whereas in minikube 0.28.0, it schedules the shutdown for one minute in the future. I don’t know if the infrastructure issues asudo shutdownin the background, but if it does and gets into a hang or race condition with itself re-issuing the command, it will never actually shutdown…Downgrading minikube from 0.28.2 to 0.27 solves everything. No need to remove directory ~/.minikube, just run
minikube deletebefore starting again.Downgrading with chocolatey:
Start
i can confirm this is occuring with windows 10 pro 1703 with minikube .28 as well. My error message is:
I will try to update this pc and see if that works, if not i will use the suggested downgrade for minikube.
upgrading to 1803 with Minikube v28 had the same results downgrading to Minikube v27 works as normal
yeah, I deleted my ~/.minikube folder + minikube virtual machine and run process : minikube start --vm-driver=x --kubernetes-version=“vx.xx.x” and works 👍
Still happening on
v0.35.0Same here:
OS: Windows 10 Pro (17134) VM-Driver: HyperV Minikube: v.0.30.0
I can shut it down with:
minikube ssh "sudo poweroff"I downgraded to 0.27 as follows:
I can then stop it with:
minikube stopSame problem here
Windows 10 Pro 1903 Docker v18.09.2 Kubectl v1.15.0 Minikube v1.2.0
Output from
minikube stop:Output from
minikube stop --alsologtostderr -v=8:I have exactly the same issue on Windows 10 pro. Stopping the cluster with
poweroffworked, but then the cluster couldn’t be started again. I had to uninstall, remove ~/.minikube and install version 0.27 for everything to work.Just had a scare with this when the kube wouldn’t stop. Just followed the simple steps from the tutorial. Thought a computer restart would do it, but it got stuck at “Restarting your computer” for about 10 minutes. Luckily, though, in the end, it actually restarted.
Same, but after reading further up it seems the developers already know this. For anyone going to the bottom of the thread first, see these workarounds:
Minkube uses docker-machin to issue a shutdown using the hypervisor management tools. this would be acpi call. Surely minikube could use an sshcommand instead, but the issue is with submachine… And this library is in maintenance mode. I also haven’t seen this issue with our fork yet… Which we are in the process of adding to minikube. I’ll keep an eye on this issue and see if the library change fixes this.
On Aug 23, 2018 09:39, “Felix Mattick” notifications@github.com wrote:
Could minikube just be updated to run that command for minikube stop?
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/kubernetes/minikube/issues/2914#issuecomment-415248809, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAHZqijtlxNuNFf-pAjewnl8leEiwSmks5uTgfCgaJpZM4Utd8V .
Just rolled up a minishift environment, based on minishift version
v1.21.0+a8c8b37, and that is capable of successfully shutting down usingminishift stop.Based on other comments, I also tried the
Stop-VM minikubecommand mentioned above. It puts a0%progress-bar in the PowerShell window, and nothing continues. Looking in the SSH, I see there is a long-running -bash command:That wasn’t there prior to the
minikube stopcommand being triggered.@gbraad I’ve certainly waited for over 1min (in fact over 5mins) and it doesn’t shutdown. My suspicions were around how Hyper-V interacts with the Linux VM but I couldn’t find anything useful to help with this. I did experiment with disabling the hyper-v integration services which includes an option for Guest OS shutdown and disabling this causes an immediate error.
I’m preparing for a talk tomorrow so don’t want to mess with my minikube installation today but can try and have another go at this later this week.