Why is Docker Desktop using so much CPU and memory on my Mac?
Last reviewed: 19 November 2026.
On a Mac, Docker Desktop runs every container inside a Linux virtual machine, so the memory and CPU you see belong to that VM rather than to individual containers. By default the VM's memory limit is half of the Mac's memory, and it keeps running while Docker Desktop is open unless Resource Saver shuts it down when idle. Lowering the CPU and memory limits in Settings > Resources and stopping containers you do not need are the direct fixes.
Which processes belong to Docker Desktop?
- Docker Desktop: the dashboard app.
- com.docker.backend: the backend that manages the VM, networking and file sharing.
- The virtual machine itself, which runs as com.apple.Virtualization.VirtualMachine when Docker uses Apple's Virtualization framework. Its memory and CPU are where your containers' work shows up.
Activity Monitor cannot show individual containers. Use docker stats in Terminal to see CPU and memory per container inside the VM.
How do you limit Docker Desktop's CPU and memory?
- Open the resource settings. Open Docker Desktop, click Settings, and go to the Advanced tab of the VM resources section (called Resources in older versions).
- Lower the memory limit. The Memory limit defaults to 50% of the Mac's memory. Reduce it to what your containers need; if it is too low, containers run short of memory inside the VM.
- Lower the CPU limit. CPU limit sets the maximum number of CPUs Docker Desktop can use.
- Keep Resource Saver on. Resource Saver shuts the Linux VM down when Docker Desktop is idle, which frees its CPU and memory. The VM restarts automatically when you run a container; Docker says that takes about 3 to 10 seconds.
- Stop idle containers. Run
docker psto see running containers anddocker stop <name>for any you do not need. Databases and dev servers keep using CPU and memory while they run.
Why is file sharing slow or CPU heavy?
Containers that read your project from macOS go through Docker Desktop's file sharing. With the Apple Virtualization framework, VirtioFS is the default and recommended implementation; gRPC FUSE is the alternative. Projects with very many small files, such as large node_modules folders mounted from the Mac, generate a lot of file-sharing work. Docker also offers Docker VMM, which it labels beta and recommends for container performance, as another Virtual Machine Manager choice.
When is Docker Desktop's resource use a problem?
A VM that holds a lot of memory while containers run is expected; Linux uses free memory inside the VM for caching. It is a problem if memory pressure on the Mac turns yellow or red, or if the VM keeps using CPU with no containers running. Check docker ps for forgotten containers, and confirm Resource Saver is on.
How can Thrum help with Docker Desktop?
Thrum's Memory tab shows memory pressure, swap, and the eight processes using the most memory, so you can see how much Docker Desktop holds and whether the Mac is short of memory. An optional alert tells you when memory pressure turns critical. Click Docker Desktop in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions
How much memory does Docker Desktop use by default on a Mac?
Docker's documentation states that the VM memory limit defaults to 50% of the host's memory. The swap file defaults to 1 GB.
Why can't I see my containers in Activity Monitor?
They run inside Docker Desktop's Linux virtual machine. Activity Monitor shows the VM as one process; docker stats shows the containers.