-
Notifications
You must be signed in to change notification settings - Fork 574
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
WSL 2 docs: Hyper-V should be enabled #445
Comments
You don't need Hyper-V to use WSL 2. You just need the |
I've got it working only after enabled hyper-v. _Does WSL 2 use Hyper-V? Will it be available on Windows 10 Home? The newest version of WSL uses Hyper-V architecture to enable its virtualization. This architecture will be available in an optional component that is a subset of the Hyper-V feature. This optional component will be available on all SKUs. You can expect to see more details about this experience soon as we get closer to the WSL 2 release._ |
Although, I still don't have network connectivity on wsl 2. Had them on wsl 1. |
HyperV isn't fully same as VM platform. In short, see this YouTube video about the different types of containers and usages. |
I've adjusted the FAQ to mention |
I did some more digging on the minimal configuration and I got it working after enabling these 3 features: Hyper-V > Hyper-V Platform > Hyper-V Services So enabling the full Hyper-V feature is not necessary. |
from Microsoft docs
So yes, WSL2 only uses some services from Hyper-V. The text can be easily misread though. |
I have Ubuntu on WSL 2 running on windows 10, and docker for desktop using WSL 2 |
Please start your own thread. |
When I first tried to use WSL 2, I got the error:
Error: 0x80370109 The operation timed out because a response was not received from the virtual machine or container.
This issue was solved by enabling hyper-v.
I was also reading that WSL 2 needs hyper-v.
So, making sure hyper-v is enabled should be included in the docs page at:
https://docs.microsoft.com/en-us/windows/wsl/wsl2-install
The text was updated successfully, but these errors were encountered: