-
Notifications
You must be signed in to change notification settings - Fork 759
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
Install fails on Windows Server 2019 #1674
Comments
Probably related to canonical/multipass#1548 |
Hi @biiiipy, thanks for raising this. I'm going to try and get access to a Server 2019 machine in order to dig a little deeper. I suspect it's related to the issue raised above where Hyper-V behaves differently on Windows Pro vs Server. |
@biiiipy this will probably take quite a bit of engineering work as we see the default switch is not created in Server 2019, so no DNS, DHCP nor NAT so internet access is a pain. If it's an option, I'd recommend using Virtualbox as the backing hypervisor for now. |
That means we need to disable hyper-v on hosts, so no windows docker containers (Hyper-V is a prerequisite for Docker runtime on Windows Server) on those hosts, making them dedicated master nodes... And that is tied to the ability to join native windows nodes to mikrok8s cluster - #1300 |
Hey @biiiipy, I believe we're going to investigate adding Windows workers to a MicroK8s cluster pretty soon so we should be able to at least give you some documentation at some point in the near future. As far as Vbox and Hyper-V go, I wasn't aware of any issues running them together, on the same host. What are you seeing when you run both? Many thanks, |
That's great to hear, can't wait! It seems that VirtualBox as of version 6.0 is able to run side by side with Hyper-V (with degraded performance though), although on the first look it seems that it only allows running 32 bit OSes. Will have to recheck this... |
Hi @biiiipy, as per #1300, we've written up the docs for getting Windows workers enrolled on a MicroK8s cluster https://discuss.kubernetes.io/t/add-a-windows-worker-node-to-microk8s/13782 |
Cool, that's great to hear! Although, why not put it on mikrok8s webpage? It will be a lot easier for other people to find... By googling a million kubernetes issues, I've never been steered to kubernetes forums... |
@biiiipy it’ll be on the microk8s docs site; we source that from discourse. It just takes a little time to update the sidebar there, so I was sharing this with you until then. Getting Multipass (thus MicroK8s) to run on Server 2019 may take some time, but I’ll leave this issue open. Thanks, |
+1 for this issue. I have a Windows Server 2019 (v1809) machine which has the same issue mentioned above. I tried switching to VirtualBox as well but VirtualBox doesn't seem to work if Hyper-V is enabled. |
+1 Idem issue in Windows Server 2019 (v1809). |
+1 also same issue in Windows Server 2022 (v21H2) |
+1, same issue for me.
Edited to add service info:
|
Any update on this? Is microk8s supported on windows server operating systems at all? |
same issue for me. (2022-08-10 microk8s-installer.exe) |
What is the latest on this? Lack of proper Windows Server support is going to force us to abandon MicroK8s, so it would be great to get a definitive answer here. |
MicroK8s on windows (and Mac) needs a VM to run on. You can provide an Ubuntu VM in whatever ways you see fit on your windows version. The MicroK8s installer uses a tool called multipass to abstract the VM provisioning. On windows multipass has two backends hyper-V and virtualbox, see [1] on how to select the right backend. I suspect that even if Hyper-V is not supported as a backend in your Windows version, Virtualbox should work. |
Would someone from Canonical be able to comment on whether we could pay them to accelerate fixing this? It sounds like microk8s / multipass would need to do some work to create the default switch and use the different Hyper-V feature name on Server 2022. |
@joedborg Any updates here? |
+1 also same issue in Windows Server 2022. |
When installing microk8s on Windows Server 2019 (runs on vmware hypervisor and has nested virtualization enabled), I get the error:
Multipass shell fails with the same error.
Btw, the suggested command seems wrong, at least for Windows Server:
But Hyper-v is installed:
![image](https://user-images.githubusercontent.com/1227867/96873454-9f3d6300-147d-11eb-86f6-8fa3b395b02e.png)
Hyper-V service is running, but has no VMs:
![image](https://user-images.githubusercontent.com/1227867/96873922-36a2b600-147e-11eb-96a5-e323dd3f79f9.png)
Any ideas where to dig?
The text was updated successfully, but these errors were encountered: