Docker VMM Enters Public Beta, Replacing Third-Party Hypervisors in Docker Desktop for Mac and Windows
Docker's self-built container hypervisor replaces libkrun on Mac and Hyper-V/WSL2 on Windows, with general availability targeted for the end of October.
Overview
Docker has opened the public beta of Docker VMM, a completely rebuilt virtual machine manager that the company describes as “a new first-party virtualization layer underneath Docker Desktop, optimized for containers,” according to Docker’s announcement. The new engine is available now on Mac and Windows starting with Docker Desktop v4.86, which Docker’s release notes list as shipping on August 10, 2026.
What We Know
Docker Desktop has historically leaned on outside virtualization software to run its Linux-native engine on other operating systems. As Cloud Native Now reported, “To date, Docker Desktop for Windows and Macs have relied on third-party VMMs – libkrun for Apple gear and Hyper-V or the Windows Subsystem for Linux for Windows.” Docker VMM replaces those backends with software the company built internally, which it says lets it “own the full stack” and “tune every part of the engine for container workloads specifically,” according to Docker’s blog post.
The new hypervisor was not built from a blank slate for this launch. Docker “first tested the technology on Docker Sandboxes, an isolated environment built for AI agents,” according to Cloud Native Now, and Docker’s own post confirms the same engine now powers both Docker Desktop and Docker Sandboxes, so that “every improvement lands in both products,” per Docker.
Docker lists four concrete areas of improvement in the beta: faster container startup “across the board, from first launch to project switches to restart recovery”; “significantly faster” file sharing between container and host; memory that gets returned to the host machine “when containers are idle”; and, on Windows specifically, a first-party VMM that combines “the isolation you’d expect from Hyper-V with the speed you’d expect from WSL2,” according to Docker’s announcement. Cloud Native Now’s independent write-up describes the same set of changes, noting that the update should mean “startup times and recoveries will happen faster” and that the desktop app “will be kinder to the host computer as well, releasing memory back to the machine when containers are idle,” per Cloud Native Now.
Enabling the beta requires no signup. On Mac, users already opted into Docker VMM in Settings are moved to the new engine automatically on upgrading to v4.86; on Windows, users switch it on from Settings > General. Docker says there is “no feature flag, no waitlist,” and that any Desktop user on v4.86 or later can turn it on today, per Docker’s blog post. Linux support will not arrive until general availability, which Docker is targeting for “the end of October 2026,” when Docker VMM is set to become the default engine for new Docker Desktop installs on Mac, Windows and Linux, according to the same post. Cloud Native Now likewise reported that “Linux users will have to wait until the software’s general release in October.”
Docker frames the rebuild as a step toward a broader goal of “a unified runtime that spans laptop, cloud, and on-prem, where containers, Compose apps, and agents are all first-class on one foundation,” according to Docker.
The rollout comes as Docker’s own usage data shows a split developer base. Citing Docker’s 2025 State of Application Development report, Cloud Native Now wrote that “about 36% of Docker development is still done on local machines, such as the developer’s laptop,” and that among platforms, “Linux is still the most popular platform for Docker, which 53% of the users deploy. But many also use macOS, which 51% of developers use. Windows is also a choice, used by 47% of developers.” Cloud Native Now also noted that Docker Desktop “is free for personal use, and begins at $11 a month ($9 a month billed annually) for professional plans.”
What We Don’t Know
Docker has not published benchmark figures to quantify the “measurably faster” startup times or “significantly faster” file I/O it claims for the beta, so the scale of the improvement over the previous libkrun and Hyper-V/WSL2 backends is not yet independently verifiable. It is also not yet clear how the beta will perform outside the workflows Docker says it is focusing on during the test period — builds, file syncs and container startup patterns — ahead of the targeted general-availability release at the end of October.
Analysis
By replacing licensed or open-source virtualization backends with software it controls end to end, Docker is betting that owning the hypervisor layer will let it ship performance and governance features on its own timeline rather than waiting on upstream projects like libkrun or Microsoft’s Hyper-V and WSL2. Routing the same engine through both Docker Desktop and Docker Sandboxes also signals that Docker sees its AI-agent sandboxing product and its traditional container-development tooling converging on shared infrastructure, rather than being built and maintained separately.