-
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
hyperv: exit status 1 - MethodInvocationNotSupportedInConstrainedLanguage #6098
Comments
Hello I may be having the same issue.
Logs:
|
My issue might be linked to Docker engine and Minikube version incompatibility. |
Hi, Will this be my issue as well in your opinion? |
@gtan01 - do you mind including the output of:
|
Hi Thomas, Here it is:
I1219 15:21:10.092819 8216 main.go:110] libmachine: [stderr =====>] :
I1219 15:21:10.434820 8216 main.go:110] libmachine: exit status 1
I1219 15:21:18.808314 8216 main.go:110] libmachine: [stderr =====>] :
I1219 15:21:19.138314 8216 main.go:110] libmachine: exit status 1
I1219 15:21:32.762612 8216 main.go:110] libmachine: [stderr =====>] :
I1219 15:21:33.099612 8216 main.go:110] libmachine: exit status 1
I1219 15:21:49.021587 8216 main.go:110] libmachine: [stderr =====>] :
I1219 15:21:49.358587 8216 main.go:110] libmachine: exit status 1
X Unable to start VM: create: precreate: exit status 1
|
It looks like PowerShell might be restricted on your computer. I found this issue which seems to indicate that other programs may suffer from the same issue: docker/for-win#1348 Do you mind trying:
Alternatively, I would talk to your IT Administrator about giving you this permission by default. Please let me know how it works! |
Hi Thomas, Thank you very much it worked in Powershell. Most appreciated. BTW, there are errors if I launch using CYGWIN FYI...below are the error messages when I run "minikube start --vm-driver=hyperv" in CYGWIN. minikube start --vm-driver=hyperv
X Unable to start VM: start: exit status 1
|
Hi Thomas, Here are the error messages. These occur when Hyperv is shutdown and restarted the next day. PS C:\WINDOWS\system32> minikube start --vm-driver=hyperv --alsologtostderr -v=1
I0106 11:15:10.526351 9328 cluster.go:114] Machine state:
W0106 11:15:11.382940 9328 start.go:1017] DeleteHost: Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
I0106 11:15:17.337547 9328 cluster.go:114] Machine state:
W0106 11:15:18.182615 9328 start.go:1017] DeleteHost: Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
I0106 11:15:29.507540 9328 cluster.go:114] Machine state:
W0106 11:15:30.359998 9328 start.go:1017] DeleteHost: Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
I0106 11:15:43.935746 9328 cluster.go:114] Machine state:
W0106 11:15:44.820295 9328 start.go:1017] DeleteHost: Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
|
Hi Thomas, I solved the problem by using "minikube delete". I notice I have to do this after complete shutdown. |
glad to see your issue was solved, I will close this, please feel free to re-open if needed. |
could be duplicate of #7990 |
The exact command to reproduce the issue
minikube start --vm-driver=hyperv
The full output of the command that failed:
minikube v1.6.1 on Microsoft Windows 10 Enterprise 10.0.17763 Build 17763
X Unable to start VM: create: precreate: exit status 1
The output of the
minikube logs
command:minikube logs
*
X api load: filestore "minikube": Docker machine "minikube" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.
The operating system version:
Windows 10 Enterprise with Hyper-V activated in BIOS also
The text was updated successfully, but these errors were encountered: