# Docker Desktop is replacing its third-party VM layer with Docker VMM Docker Desktop 4.86 puts Docker’s rebuilt first-party VMM into public beta on Mac and Windows, replacing the third-party virtualization layer under its Linux VM and giving Docker direct control over startup, file I/O, memory reclamation and future runtime governance. Docker VMM is now an opt-in public beta on Mac and Windows in Docker Desktop 4.86. The architectural change matters more than Docker’s vendor performance claims: Desktop’s hidden VM layer is becoming a first-party runtime shared with Docker Sandboxes, with GA targeted for late October. - Status: Active - Published: 2026-08-20T22:31:49+12:00 - Updated: 2026-08-20T22:31:49+12:00 - Categories: Web Development, Cloud & Infrastructure, Deployment & DevOps, Developer Tools - Tags: Docker, Docker Desktop, Docker VMM, virtualization - Canonical HTML: https://beyondthe.news/dossiers/docker-vmm-public-beta-desktop-virtualization ## What changed Docker has rebuilt the virtual-machine monitor used underneath Docker Desktop as a first-party component. Docker VMM is available in public beta in Desktop 4.86 on macOS and Windows; Docker says it replaces the third-party VMM Desktop previously relied on. On Mac, existing Docker VMM users receive the rebuilt engine with the upgrade; on Windows users can explicitly opt in. Linux support is planned for GA. ## Why it matters Docker Desktop runs a Linux VM on non-Linux hosts, so the VMM sits beneath every local container workflow even though most developers rarely interact with it directly. Owning that layer gives Docker a single place to tune startup, host/container file sharing, memory reclamation, isolation and future admin controls. Docker also says the same virtualization engine powers Docker Sandboxes, pointing toward a shared runtime for ordinary containers and agent sandboxes. For builders, this could change the performance and resource profile of day-to-day local development without requiring application changes, but the public beta should be treated as a runtime migration that needs workload-specific validation. ## The invisible layer under Docker Desktop is changing Docker Desktop cannot run its Linux-native engine directly on macOS or Windows, so it creates and manages a Linux VM. A VMM handles that VM. Docker says Desktop previously depended on a third-party VMM; the new Docker VMM is built and maintained in-house and is tuned specifically for container workloads. That gives Docker control over a layer that influences startup, networking, file sharing, memory behavior and isolation. ## The beta spans both Mac and Windows Docker VMM ships with Docker Desktop 4.86. Mac users who were already using Docker VMM are moved to the rebuilt engine on upgrade. Windows users can opt in under Settings > General. Docker says there is no waitlist or separate feature flag, while Linux support is planned for the GA release. ## Docker is making performance claims, not yet publishing neutral benchmarks Docker says the rebuilt VMM improves container startup, host-container file I/O, idle-memory return and Windows stability. Those claims are directionally important because edit-build-test loops and Desktop memory retention are common friction points, but Docker’s announcement does not provide broad independent benchmark data across real repositories and host configurations. Teams should therefore benchmark their own monorepos, bind mounts, databases and multi-container stacks before standardizing on the beta. ## The shared engine with Sandboxes is the longer-term signal Docker says the same virtualization engine also powers Docker Sandboxes and describes a longer-term direction toward one runtime spanning laptops, cloud and on-prem environments with containers, Compose applications and agents on the same foundation. The immediate release is a Desktop beta, but the architectural consequence is that local container development and isolated agent execution are converging on a common Docker-controlled virtualization layer. ## Key details - Announced August 12, 2026. - Available in public beta starting with Docker Desktop 4.86. - Runs on macOS and Windows in the beta; Docker says Linux support will arrive at GA. - Docker says Desktop previously relied on a third-party VMM and the new engine is first-party. - Docker claims faster startup, better host/container file I/O, improved memory reclamation and better Windows stability. - The virtualization engine is also used by Docker Sandboxes. - Docker targets general availability for the end of October 2026, when it plans to make Docker VMM the default for new Docker Desktop installs. ## Builder takeaways - Benchmark representative local workloads before enabling the beta across a team, especially repositories with heavy bind-mount I/O, databases or many Compose services. - Watch host memory after idle periods and repeated container restarts; memory reclamation is one of Docker’s explicit design goals and a useful migration check. - Treat this as a runtime-layer change even if application code is untouched: keep an easy rollback path while the feature remains beta. - Teams using both Docker Desktop and Docker Sandboxes should watch for shared runtime controls, because improvements or regressions in the VMM may increasingly affect both environments. ## What to watch - Independent performance measurements across Mac and Windows hardware and common development stacks. - Whether the late-October GA target holds and whether Docker VMM becomes the default exactly as described. - Which enterprise administration and governance controls Docker adds once the VMM becomes the common foundation for Desktop and Sandboxes. ## Uncertainties - The performance improvements cited in the announcement are vendor claims; Docker did not provide broad independent benchmark evidence in the release post. - The product remains in public beta, so behavior, defaults and the GA schedule can still change. ## Sources - [Docker VMM Public Beta: A Complete Overhaul, Built for Performance](https://www.docker.com/blog/docker-vmm-public-beta/) — Docker · official announcement · 2026-08-12T00:00:00+12:00. Primary source for architecture, availability, claimed performance changes and GA plans.