Source: Docker Blog — 2026-08-12
Summary
Docker released a public beta of Docker VMM, a virtualization layer for Docker Desktop on Mac and Windows (v4.86+) that Docker built and owns end-to-end, replacing the third-party VMM library the product previously relied on. The company claims measurably faster container startup, quicker host-container file I/O, and idle-memory reclamation that returns RAM to the host once containers go idle; on Windows specifically, it targets Hyper-V-level isolation running at WSL2-level speed. General availability, when Docker VMM becomes the default engine on Mac, Windows, and Linux, is targeted for the end of October 2026.
Key Takeaways
- Docker VMM replaces the third-party virtual machine monitor Docker Desktop previously shipped with a hypervisor layer Docker wrote and controls itself, letting it tune specifically for container workloads instead of general-purpose VM use cases.
- The beta claims measurably faster container startup across first launch, project switches, and restart recovery, plus significantly faster file sharing between host and container.
- Idle containers no longer hold onto host RAM — Docker VMM reclaims memory back to the host when containers aren't active, addressing a long-standing Docker Desktop memory complaint.
- On Windows, the pitch is Hyper-V-grade isolation at WSL2-grade speed — historically a tradeoff, since Hyper-V isolation carried a performance tax that WSL2-backed engines avoided.
- The same virtualization engine also powers Docker Sandboxes (SBX), signaling a bet on one shared foundation for containers, Compose apps, and agent workloads across laptop, cloud, and on-prem — with GA targeted for the end of October 2026, when Docker VMM becomes the default engine on Mac, Windows, and Linux alike.
Reel Script
Hook: Docker just replaced a piece of infrastructure most developers never think about — the hypervisor underneath Docker Desktop — with one it built entirely in-house. The claim: faster container startups, faster file syncs, and Windows isolation that no longer forces you to choose between security and speed.
Core Concept: Docker containers are a Linux-kernel feature, so on Mac and Windows, Docker Desktop can't run them natively — it spins up a lightweight virtual machine that hosts a real Linux kernel, and every container lives inside that VM. The software managing that VM, the virtual machine monitor, previously came from a third-party library Docker didn't fully control, which meant Docker could only tune container performance as far as that borrowed layer allowed. Docker VMM tears that dependency out and replaces it with virtualization code Docker wrote itself, giving it direct control over how the VM boots, how it shares files with the host, and how it manages memory. That direct control is what unlocks the performance claims: startup speed, file I/O, and memory reclamation are all things a VMM governs directly, and Docker can now optimize each one specifically for container workloads instead of accepting general-purpose VM tradeoffs designed for other use cases.
Hands-On: The concrete before-and-after is worth putting on screen as a comparison. Before, on Windows: Docker Desktop's WSL2-backed engine was fast but shared the WSL2 kernel more loosely, while a Hyper-V-isolated engine was safer but noticeably slower — a straight security-versus-speed tradeoff. After: Docker VMM claims Hyper-V-grade isolation running at WSL2-grade speed, closing that gap for Windows developers for the first time with a VMM Docker itself builds and maintains. On memory: before, an idle container's Docker Desktop VM would sit there holding onto host RAM whether or not any workload was actually running; after, Docker VMM actively hands that memory back to the host once containers go idle. On startup: Docker measures improvements not just on cold first launch, but across the everyday cases developers hit repeatedly — switching between projects and recovering from a restart — all reported as measurably faster.
Turning it on differs by platform. On Mac, if you were already opted into the earlier Docker VMM setting, upgrading to Docker Desktop v4.86 switches you onto the new engine automatically — no action needed. On Windows, it's a new opt-in toggle under Settings > General labeled "Docker VMM." Beta runs through fall 2026, with Docker specifically watching build performance, file-sync behavior, and container startup patterns for regressions before it commits further. General availability is targeted for the end of October 2026, at which point Docker VMM stops being an opt-in beta and becomes the default engine for every new Docker Desktop install — across Mac, Windows, and Linux, the last of which skips the beta entirely and jumps straight to GA.
Takeaway: This isn't a checkbox beta — it's Docker replacing a foundational dependency it never fully controlled, and the Windows isolation-versus-speed tradeoff finally closing is the detail worth caring about most. If you run Docker Desktop on Windows or Mac, flip on Docker VMM in v4.86+ now and benchmark your own startup and file-sync times before GA locks it in as default.