Troubleshoot Docker Desktop: Virtualization Support Error – wiki基地

Troubleshoot Docker Desktop: Virtualization Support Error (Windows)

If you’re encountering a “Virtualization Support Error” with Docker Desktop on Windows, follow these steps:

• Enable Virtualization in BIOS/UEFI:

  • Restart your computer.
  • Enter your BIOS/UEFI settings (common keys: F2, Delete, F10, F12, Esc, depending on manufacturer).
  • Locate settings like “Virtualization Technology,” “Intel VT-x,” “AMD-V,” or “SVM Mode.”
  • Ensure this setting is Enabled.
  • Save changes and exit BIOS/UEFI.

• Enable Required Windows Features:

  • Search for “Turn Windows features on or off” in the Windows search bar and open it.
  • Ensure the following features are checked:
    • Hyper-V (for Windows Pro/Enterprise)
    • Virtual Machine Platform
    • Windows Subsystem for Linux
    • Windows Hypervisor Platform
  • Click “OK” and restart your computer if prompted.

• Verify WSL2 Installation and Version:

  • Open PowerShell or Command Prompt as an administrator.
  • Run wsl --install to ensure WSL is installed.
  • Run wsl --set-default-version 2 to set WSL2 as the default.
  • Check installed distributions and their versions with wsl -l -v. If any distribution is WSL1, convert it to WSL2 using wsl --set-version <distro-name> 2.

• Check for Conflicts:

  • Ensure no other virtualization software (like VirtualBox or VMWare) is actively conflicting with Hyper-V or WSL2.

• Reset Virtualization Stack (Advanced, if issues persist):

  • Open Command Prompt as Administrator.
  • Run: bcdedit /set hypervisorlaunchtype off
  • Disable “Hyper-V,” “Virtual Machine Platform,” and “Windows Subsystem for Linux” in “Turn Windows features on or off.”
  • Reboot your computer.
  • Re-enable the features in “Turn Windows features on or off.”
  • Open Command Prompt as Administrator.
  • Run: bcdedit /set hypervisorlaunchtype auto
  • Reboot again.

• Windows Home Edition Specifics:

  • Hyper-V is not available. Docker Desktop relies solely on WSL2. Ensure WSL2 is correctly installed and configured as per the steps above.

I will now provide the troubleshooting steps for macOS users in the next response.