-
Notifications
You must be signed in to change notification settings - Fork 302
Closed
Description
Enabling Windows Containers feature is failing when Hyper-V is not installed. In theory this feature should not be required for running Windows Containers with process level isolation only.
Expected behavior
Docker Desktop should switch to a context which would allow running windows containers with process level isolation only.
Actual behavior
An Error occurred:
Required Windows feature(s) not enabled: Hyper-V.
Docker Desktop will exit.
Nice to have
I'm not an expert, but in theory Virtual Machine Platform feature is also running a Hyper-V what in theory together with Windows Hypervisor Platform should allow running containers with hyperv isolation.
Information
- Windows Version:
20H2Windows 10 Pro - Docker Desktop Version: `2.5.1.0 (49923)
- Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No
- Installed Windows Features:
- Hyper-V
- Containers
- Virtual Machine Platform
- Windows Hypervisor Platform
- Windows Subsystem for Linux
- For Linux containers I'm using WSL2, everything works perfect. I've uninstaller the Hyper-V because virtual network card drivers added not accepted latency to my Windows machine for real time audio processing.