Pick your symptom
Each link below jumps to a deep-dive page on a single class of error. If the symptom you’re seeing isn’t covered, skip to the “diagnostic basics” section further down — it covers the steps that resolve the long tail.
WSL 2 not working
"WSL 2 installation is incomplete", failed distro deploys, kernel update failures.
Virtualization not enabled
BIOS/UEFI walkthroughs to turn on Intel VT-x and AMD-V/SVM.
Hyper-V conflicts
Run Docker Desktop alongside VirtualBox and VMware Workstation.
Mac permission errors
Privileged-helper prompts, denied bind mounts, Full Disk Access.
Diagnostic basics that resolve most issues
Before going deep on a specific error class, four checks resolve a surprising fraction of intermittent or vague Docker Desktop problems.
1. Update Docker Desktop and the OS itself
The Docker engineers fix WSL 2 quirks, Hyper-V interaction regressions, and Apple Silicon edge cases in nearly every release. The same goes for macOS point releases and Windows cumulative updates. If you’re multiple versions behind, the fix you’re looking for may already exist.
2. Restart with a clean state
Docker Desktop → bug icon (Troubleshoot) → Restart. If that doesn’t help, escalate to Reset to factory defaults — it wipes containers, images, and volumes, but keeps your license and account.
3. Capture diagnostics before you ask for help
The diagnostic bundle (Troubleshoot → Get support → Upload diagnostics) contains the engine logs, VM logs, and a snapshot of your settings. If you ever need to file a bug on the official tracker, attaching a recent diagnostic ID gets you triaged in hours instead of days.
4. Confirm the engine is actually running
On all platforms, the cheapest sanity check is:
$ docker info Server: Containers: 0 Running: 0 Server Version: 27.2.0 ...
If docker info prints server-side fields, the engine is up and reachable. If it errors out with Cannot connect to the Docker daemon, the engine isn’t running — that’s when one of the four focused troubleshooting pages comes in.
Frequently asked questions
Why is Docker Desktop not starting?
The four most common causes are a missing or outdated WSL 2 kernel on Windows, hardware virtualization disabled in BIOS, a Hyper-V conflict with VirtualBox/VMware, and a stuck privileged-helper prompt on macOS. Each has a dedicated guide linked from this page.
How do I view Docker Desktop logs?
Open Docker Desktop → click the bug icon (Troubleshoot) → "Get support" → "Upload diagnostics". The diagnostic bundle is written to your home directory and can be inspected directly. On Linux you can also run `journalctl --user -u docker-desktop -f` for the live system log.
How do I reset Docker Desktop without uninstalling?
Open Docker Desktop → click the bug icon (Troubleshoot) → "Reset to factory defaults". This wipes all containers, images, and local volumes but keeps your account, license, and settings. It fixes most "engine refuses to start" cases on Windows and macOS.
Should I use the WSL 2 or Hyper-V backend on Windows?
WSL 2 is the default and recommended backend in 2026. It is faster, uses less memory, and integrates better with the Windows file system. Use Hyper-V only if you have a specific compatibility reason — for example, if your organization disables WSL by policy.