Enforce WSL2 (Can't run docker on Windows 10 Home with Hyper-V)

[JoPark20]

I installed xud ui, downloaded docker and installed docker, rebooted - so far all good.
But as i am using windows 10 home i can't get docker running, see pop up:

this leads to en ever loading xud screen:

[kilrau]

Thanks for opening this issue! This is not related to Windows Home (docker works fine on Windows home, see https://docs.docker.com/docker-for-windows/install-windows-home/), but that your computer's motherboard has hardware virtualization switched off. You will need to enable it via the BIOS menu. I can help you with this on discord in a 1-1 session.

Since unfortunately there is nothing much we can do to "fix" it, I wonder what computer motherboard you have. I was convinced most modern motherboards have virtualization enabled by default :/

[JoPark20]

Ah thanks for the additional information - I got the link (same from screenshot: https://docs.docker.com/docker-for-windows/troubleshoot/#virtualization), which lead my to Hyper V.. And here I read about that this feature is only available for Windows Enterprise / Pro.
Will write you this evening / tomorrow the specs.

[kilrau]

Thanks for reporting back. Here is the problem:

• Docker needed Hyper-V to be enabled to work up until the official release of WSL2 in May this year.
• Docker refers to WSL2 as "default" now and Hyper-V as "legacy" backend.
• Windows 10 Home does not include Hyper-V, but it does include WSL2
• WSL2 is supported from Windows 10 version 1903 already, which everyone should be running by now

Since on top of all that, WSL2 is much more stable for our linux containers, I think it's time to force Hyper-V out.

Todo's for this issue:
Step 1. Disable Hyper-V fallback and always bring up WSL2 installation (even though that means opening a browser tab asking user to download the WSL2 exe and install it manually). I closed #87.
Step 2: Detect if Virtualization is not enabled, there must be a Windows System call for that, it's shown in the taskmanager's performance tab:

Step 3: Continue investigating how an unattended WSL2 installation could be achieved: I opened microsoft/WSL#6201, the answer there refers to "wsl --install" which should solve this indeed. I am trying to find out when it will be available.

[kilrau]

Watch microsoft/WSL#6201 (comment)

[kilrau]

So downloading the WSL2.exe and installing via Powershell is already possible, just that the user would need confirm an admin prompt. Let's give this a shot @erkarl