-
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
Support for Hyper-V on Windows #465
Comments
We can easily enable hyperv, will send in a PR soon-ish unless someone else gets there soon. As for making it default, please comment on #270 |
We're still doing some testing here, we should get it in soon. |
ref #476 |
Wohoooo!!! @dlorenc can you please make a new release with this update! |
We'll try to get a release out early next week. In the meantime we have a CI job that does builds at each PR. You can grab this commit here: (467 is the PR id) https://storage.googleapis.com/minikube-builds/467/minikube-windows-amd64.exe |
We should add some hyper-v docs to the drivers documentation page. I think @aaron-prindle had to do some manual configuration with the virtual switch. |
We're waiting for new release with this update! |
We're going to cut 0.9 later today! |
Any progress on this? Is it supported with 0.12? |
@rodcloutier It was supposed to be fixed but there are some new issues with minikube, some are probably not related to Hyper-V but some are. |
I have a similar issue on Windows 10 pro: $ docker-machine create -d virtualbox default
Running pre-create checks...
Error with pre-create check: "This computer is running Hyper-V. VirtualBox won't boot a 64bits VM when Hyper-V is activated. Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)" Without the vtx check though, it's stuck on '(default) Waiting for an IP...' $ docker-machine create -d virtualbox --virtualbox-no-vtx-check default
Running pre-create checks...
Creating machine...
(default) Copying C:\Users\cobalt\.docker\machine\cache\boot2docker.iso to C:\Users\cobalt\.docker\machine\machines\default\boot2docker.iso...
(default) Creating VirtualBox VM...
(default) Creating SSH key...
(default) Starting the VM...
(default) Check network to re-create if needed...
(default) Waiting for an IP... |
=( |
Any update on this? I would like to run Minikube on Windows 10 64 bit machine with Hyper-V (not VirtualBox). Thanks |
Is Hyper-V supported yet? I get the error: "The connection to the server localhost:8080 was refused - did you specify the right host or port?" with a clean install of kubectl and docker-ce |
Yes, it is currently supported. If you can post a new github issue with some information on your virtual switch configuration and how you attempted to start minikube we can help investigate the issue that you are having. |
@aaron-prindle You have mentioned minikube is supported with Hyper-V , however I am not able to use it with the latest release that was done only yesterday. I still get hyper-v not a valid driver message , What am I missing |
@srivathsah I used the following command on Windows 10 Pro, this is with version 0.20.0 of minikube
You would need to replace the "Primary Virtual Switch" with whatever you have, It worked for me on my local machine, hope this helps. |
I'm running 0.20.0 and have Hyper-V and the added virtual switch, but when I try to start it still thinks I'm using VirtualBox: Details: 00:00:01.200078 Power up failed (vrc=VERR_VMX_NO_VMX, rc=E_FAIL (0X80004005)). Retrying. |
I have Hyper-V enabled on my Windows for Docker. When I try to run minkube cluster, it says that I have to disable Hyper-V for VirtualBox to work or use Hyper-V as the driver but Hyper-V is not supported by minikube.
I purpose that Hyper-V be supported by minikube as the default driver for Windows.
The text was updated successfully, but these errors were encountered: