{"id":4793,"date":"2026-08-12T18:21:52","date_gmt":"2026-08-12T18:21:52","guid":{"rendered":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/08\/12\/docker-vmm-public-beta-a-complete-overhaul-built-for-performance\/"},"modified":"2026-08-12T18:21:52","modified_gmt":"2026-08-12T18:21:52","slug":"docker-vmm-public-beta-a-complete-overhaul-built-for-performance","status":"publish","type":"post","link":"https:\/\/rssfeedtelegrambot.bnaya.co.il\/index.php\/2026\/08\/12\/docker-vmm-public-beta-a-complete-overhaul-built-for-performance\/","title":{"rendered":"Docker VMM Public Beta: A Complete Overhaul, Built for Performance"},"content":{"rendered":"

Today we\u2019re announcing the public beta of a fully rebuilt Docker VMM: a new first-party virtualization layer underneath Docker Desktop<\/a>, optimized for containers, and now available on both Mac and Windows starting with Docker Desktop v4.86.\u00a0<\/p>\n

\n What\u2019s Changed, and Why It Matters
\n <\/h2>\n

\n<\/p>

Part of the magic of Docker Desktop is how it provides a seamless deployment of the Linux-native Docker engine on other platforms, like macOS and Windows. To support that, Desktop automatically creates and manages a VM and all the complicated integration of your local network and filesystem, in a safe and performant way.\u00a0<\/p>\n

Creating that VM is the job of a virtual machine monitor, the layer that sits between your hardware and the containers Docker runs. Most developers never think about it. But when it\u2019s slow, unstable, or holding onto your machine\u2019s memory it should have released, you notice it constantly.\u00a0<\/p>\n

Docker Desktop has always relied on a third-party VMM for this. Now it runs on Docker VMM, built by us from the ground up. That means we own the full stack, and we can tune every part of the engine for container workloads specifically. That translates directly to you: an engine that improves continuously, responds to developer feedback, and ships on our own schedule.<\/p>\n

This matters for everyone running Docker Desktop today. Performance, stability, and governance improvements at the virtualization layer enhance the experience across the board, for every workflow, on every team.<\/p>\n

\"Isometric<\/figure>\n

Image 1: Isometric diagram of the Docker stack: Host, DockerVMM, and Docker Engine layers.<\/p>\n

The Performance Improvements Are Real <\/h2>\n

Here\u2019s what you\u2019ll notice when you start using the beta release of Docker VMM:<\/p>\n

Faster startup. <\/strong>Container startup is measurably faster across the board, from first launch to project switches to restart recovery.\u00a0<\/p>\n

Better file I\/O. <\/strong>File sharing between container and host is significantly faster. When you\u2019re in an edit-compile-test loop, you\u2019ll see improvements every single build.\u00a0<\/p>\n

Smarter memory management. <\/strong>Docker VMM returns memory to the host when containers are idle, so Docker Desktop isn\u2019t holding onto RAM you\u2019re not using.\u00a0<\/p>\n

Improved stability on Windows.<\/strong> For the first time, Windows developers get a VMM built and maintained by Docker, with performance and stability work coming straight from us.<\/p>\n

Stronger isolation, better performance. <\/strong>DockerVMM still runs in a fully isolated VM, optimized for performance. On Windows, that means the isolation you\u2019d expect from Hyper-V with the speed you\u2019d expect from WSL2.\u00a0<\/p>\n

\n One Engine, Everywhere You Run Docker
\n <\/h2>\n

\n<\/p>

The virtualization engine powering Docker VMM also powers Docker Sandboxes (SBX). That\u2019s not a coincidence; it\u2019s intentional. Every improvement lands in both products, so you get them wherever you choose to run Docker.\u00a0<\/p>\n

This matters beyond performance. As we build deeper capabilities into the engine, including enterprise admin controls and tighter governance for dev environments, they surface across both products. Longer term, we\u2019re building toward a unified runtime that spans laptop, cloud, and on-prem, where containers, Compose apps, and agents are all first-class on one foundation. Docker VMM is how Docker Desktop gets there, and this is step one.\u00a0<\/p>\n

How To Enable It <\/h2>\n

On Mac:<\/strong> If you are already using Docker VMM in Settings, you will be automatically updated to the new engine when you upgrade to v4.86.\u00a0<\/p>\n

On Windows:<\/strong> Open Settings > General and you will see a new \u201cDocker VMM\u201d option. Switch it to opt in.\u00a0<\/p>\n

\"Feature<\/figure>\n

Image 2: Feature Flag for Docker VMM in Settings\u00a0<\/p>\n

No feature flag, no waitlist. Any Docker Desktop user on v4.86 or later can switch today.\u00a0Note: Linux support will be available at GA.\u00a0<\/em><\/p>\n

\n What\u2019s Next
\n <\/h2>\n

Beta runs through fall, focused on real developer workflows: builds, file syncs, and the container startup patterns you hit every day.\u00a0<\/p>\n

GA is targeted for the end of October 2026, when Docker VMM becomes the default engine for new Docker Desktop installs across Mac, Windows, and Linux. GA is the baseline, and from there, the pace picks up. Everything we build next sits on this foundation.\u00a0<\/p>\n

Try It Today <\/h2>\n

Update to Docker Desktop v4.86<\/a> to get started.\u00a0<\/p>\n

Noticing a difference? Have ideas for where you\u2019d want us to go next? We\u2019re collecting feedback through in-product<\/a> responses, our community Slack<\/a>, and support<\/a> channels.\u00a0<\/p>\n

This is the best Docker Desktop has ever run, and it only gets better from here.\u00a0<\/p>\n

Learn more<\/h3>\n