CPU requirements: Hyper-V (I believe since Server 2012 R2) requires a 64-bit CPU with VT-X/ AMD-v and SLAT (second level address translation).However, some VMWare Workstation users seem to have noticed performance issues when VMWare is using the Hyper-V backend and may prefer to disable Hyper-V for that reason. Some virtualisation products like VMWare Workstation solve this by utilising HyperV as their backend.

When Hyper-V is enabled other (low level) virtualisation engines won’t work anymore.(A quote from Docker Captain Bret Fisher: “I have worked with orgs that aren’t allowed to run any VM locally without a full security audit of the solution, and only ‘approved’ VM’s can be run.”) you don’t want to or can’t easily run VMs on a Windows machine for security compliance reasons and would like to treat Windows containers as Windows processes and not VMs.I’ve seen three common reasons why users might be unable to enable Hyper-V on their Windows system: WSL2 in turn also uses Hyper-V - so without having Hyper-V enabled Docker Desktop fails to start and can’t be used.

The problemĭocker Desktop on Windows 10 supports two backends: HyperV and WSL2. What if you want to run Docker on Windows 10 but can’t or don’t want to enable Hyper-V? Here’s a solution for running both Windows and Linux containers on Windows 10 entirely without Hyper-V and without Docker Desktop. Running Windows and Linux containers on Windows 10 is possible without HyperV.

Wsl 2 virtualbox