Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug Report
Environment:
Minikube version : v0.24.1
cat ~/.minikube/machines/minikube/config.json | grep -i ISO
or minikube ssh cat /etc/VERSION
): minikube-v0.23.6What happened: Tried running minikube.exe start --hyperv-virtual-switch base --vm-driver hyperv -v 7
and it failed
What you expected to happen: Minikube should start for the first time
How to reproduce it (as minimally and precisely as possible): run the command above
Output of minikube logs
(if applicable):
```E:\Minikube>minikube.exe start --hyperv-virtual-switch base --vm-driver hyperv -v 7
Starting local Kubernetes v1.8.0 cluster...
Starting VM...
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Get-VM minikube ).state
[stdout =====>] :
[stderr =====>] : Get-VM : Hyper-V was unable to find a virtual machine with name "minikube".
At line:1 char:3
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Start-VM minikube
[stdout =====>] :
[stderr =====>] : Start-VM : Hyper-V was unable to find a virtual machine with name "minikube".
At line:1 char:1
E1201 23:16:48.643261 14168 start.go:150] Error starting host: Error starting stopped host: exit status 1.
Retrying.
E1201 23:16:48.653249 14168 start.go:156] Error starting host: Error starting stopped host: exit status 1
```
Anything else do we need to know: I have docker installed but the docs say that shouldn't interfere.
I had the same as well.
I got round it by deleting the .minikube folder in my User Account, as detailed here: http://www.dotjson.uk/minikube-w10/
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
May be it will help to remove the .minikube or .kube folders in %USERPROFILE%
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
I had the same as well.
I got round it by deleting the .minikube folder in my User Account, as detailed here: http://www.dotjson.uk/minikube-w10/
Thanks @JonJam . Deleting the .minikube folder helped out :)
Most helpful comment
I had the same as well.
I got round it by deleting the .minikube folder in my User Account, as detailed here: http://www.dotjson.uk/minikube-w10/