Skip to content

docs: refer to Docker VMM as a virtual machine manager #26134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dvdksn merged 1 commit into from
Sep 21, 2026
+4 −2
Merged

docs: refer to Docker VMM as a virtual machine manager #26134

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions content/manuals/desktop/features/vmm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,9 @@ Docker Desktop supports multiple Virtual Machine Managers (VMMs) to power the Li

{{< summary-bar feature_name="VMM" >}}

Docker VMM is a container-optimized hypervisor. From Docker Desktop 4.86, Docker VMM uses Docker's own hypervisor, replacing `libkrun` used in version 4.35 - 4.85 for Mac users. Built specifically for container workloads, Docker VMM:
Docker VMM is a container-optimized virtual machine manager. Starting with
Docker Desktop 4.86, it uses Docker's own VMM implementation instead of
`libkrun`, which was used in versions 4.35 through 4.85 on Mac. Built specifically for container workloads, Docker VMM:

- Returns idle memory to the host when containers aren't active, so Docker Desktop doesn't hold RAM it's not using
- Improves file I/O between container and host, reducing latency in the edit-compile-test loop
Expand All @@ -39,7 +41,7 @@ Docker VMM requires a minimum of 4 GB of memory allocated to the Docker Linux VM
If you previously had Docker VMM selected, which engine runs depends on your version:

- Docker Desktop 4.35 and earlier is backed by `libkrun`
- Docker Desktop 4.86 and later is backed by Docker's own hypervisor
- Docker Desktop 4.86 and later uses Docker's own VMM implementation

If you're upgrading from version 4.35 onwards, your setting is preserved and Docker Desktop switches to the new Docker VMM automatically on restart.

Expand Down