Quick reference
- CPU: 64-bit, with hardware virtualization extensions enabled.
- RAM: 8 GB strongly recommended; 4 GB is the documented minimum but cramped.
- Disk: 6 GB free, more if you pull large images.
- Backend: WSL 2 on Windows, Apple Virtualization framework on macOS, KVM on Linux.
Windows
| Operating system | Windows 10 64-bit (21H2 or higher) or Windows 11 (Home, Pro, Enterprise, Education) |
|---|---|
| Architecture | x64 (Intel/AMD) or ARM64 (Snapdragon X, Surface Pro 11) |
| Processor | 64-bit with SLAT |
| Memory | 4 GB minimum, 8 GB recommended, 16 GB for heavy stacks |
| Backend | WSL 2 (recommended) or Hyper-V |
| BIOS | Hardware virtualization (Intel VT-x or AMD-V) enabled |
| Disk space | ~6 GB free for Docker Desktop and base images |
| Windows features | VirtualMachinePlatform and HypervisorPlatform enabled |
macOS
| Operating system | macOS 13 Ventura, 14 Sonoma, or 15 Sequoia |
|---|---|
| Architecture | Apple Silicon (M1/M2/M3/M4) or Intel x86_64 |
| Memory | 4 GB minimum, 8 GB recommended |
| Disk space | ~6 GB free |
| Rosetta 2 | Required on Apple Silicon to run x86 images under emulation |
| Permissions | Admin account for the privileged-helper install |
Linux
| Distributions | Ubuntu 22.04 / 24.04, Debian 11 / 12, Fedora 39+, RHEL 9, Arch (AUR) |
|---|---|
| Architecture | x86_64 or arm64 |
| Processor | 64-bit with KVM virtualization support |
| Memory | 4 GB minimum, 8 GB recommended |
| Init system | systemd |
| Desktop environment | GNOME, KDE, or MATE recommended |
| Disk space | ~6 GB free |
| Permissions | Membership in the kvm group; /dev/kvm accessible |
Why each requirement exists
Hardware virtualization
The engine runs inside a Linux VM on Windows and macOS; the VM in turn relies on the host CPU’s hardware virtualization extensions (Intel VT-x, AMD-V/SVM) to be fast. Without them, Docker Desktop refuses to start. If Task Manager shows Virtualization: Disabled, the option needs flipping in BIOS — see enabling virtualization.
RAM
4 GB is the minimum because the VM, the engine, and a single small container have a hard floor of about 1.5 GB of memory. Add a database, a backend service, and a frontend dev server and you’re past 4 GB on a normal workday. 8 GB is comfortable for typical Compose stacks; 16 GB is ideal if you’re running Kubernetes locally.
Disk space
~6 GB covers Docker Desktop itself plus the base VM image and a couple of small base images. The number grows quickly with real workloads — popular stacks easily reach 20–40 GB once Postgres data volumes, build caches, and a few large language images accumulate. Plan for it on small SSDs.
Backend choices
On Windows, Docker Desktop’s WSL 2 backend uses the Windows Hypervisor Platform — coexists cleanly with VirtualBox 7+ and VMware Workstation 16+. On macOS, Docker Desktop uses Apple’s Virtualization framework (modern Macs) or the legacy HyperKit on older systems. On Linux, the engine VM runs directly on KVM.
Permissions
Docker Desktop needs to install privileged components (a Windows service on Windows, a launchd helper on macOS, a per-user systemd unit on Linux). On all three platforms, the install requires administrator rights. Running as a standard user blocks the engine before it even starts.
When you should consider an alternative
- Older Macs (pre-2019). The Apple Virtualization framework is supported but file-sharing performance lags. Consider OrbStack on supported hardware.
- Underpowered Windows laptops. If you’re on 4 GB RAM with no upgrade path, lightweight options like Podman Desktop run leaner.
- Servers and CI runners. Docker Engine alone is the right choice — no VM, no GUI, no Desktop license. See the Linux download page for the engine-only path.