Why is Docker Desktop using so much memory and CPU on my Mac?
Last reviewed: 19 November 2026. Paths, defaults and settings taken from Docker's documentation; not installed on the Mac used for checking.
Docker Desktop runs your containers inside a Linux virtual machine, and that machine is allowed up to 50% of your Mac's memory by default plus a 1 GB swap file. It uses CPU whenever containers run or images build. Lower the CPU and memory limits in Settings > Resources, keep Resource Saver on, and quit Docker Desktop when you are not using it.
Docker Desktop at a glance
| Docker Desktop | |
|---|---|
| Made by | Docker, Inc. |
| Type | App |
| Location | /Applications/Docker.app |
| Runs as | your user |
| Can you quit it? | Yes. Quitting it stops Docker and all running containers until you open it again. |
What is Docker Desktop?
Docker Desktop is the Mac app (/Applications/Docker.app) that runs Docker containers. A Mac cannot run Linux containers directly, so Docker Desktop starts a lightweight Linux virtual machine that holds the Docker daemon and your containers, and connects it to the Mac's files and network.
Several processes share the work: the Docker Desktop app itself, its backend process com.docker.backend, the privileged helper com.docker.vmnetd, and the virtual machine. The docker command-line tools ship inside the app at /Applications/Docker.app/Contents/Resources/bin.
Is Docker Desktop safe?
Yes. Docker Desktop is a widely used developer tool. Docker documents that the app itself runs as your user, and that containers running as root inside the virtual machine do not get root access to the Mac.
Why does Docker Desktop use so much memory, CPU and disk?
- The virtual machine's memory limit. Docker Desktop's memory limit is RAM allocated to its Linux virtual machine, and it defaults to 50% of the Mac's memory. On a 16 GB Mac that allows up to 8 GB for Docker.
- Running containers. Containers keep running in the background until stopped. Databases, message queues and development servers use CPU even when you are not looking at them.
- Image builds and emulation. Building images is CPU-heavy. Running x86_64 (Intel) images on Apple silicon needs emulation; Docker offers a Use Rosetta setting to speed this up, off by default.
- Images, volumes and build cache. Pulled images, volumes and the build cache are stored inside Docker's virtual disk, up to the disk usage limit in Settings.
How much memory is normal for Docker Desktop?
While containers run, several gigabytes of memory for Docker is normal, up to the limit you set. With no containers running, Resource Saver stops the virtual machine after 5 minutes by default, and Docker's footprint drops by 2 GB or more according to Docker.
CPU use follows what the containers are doing; an idle stack should settle to a low level.
How do you stop Docker Desktop from using so much memory?
- Stop idle containers. Stop containers you are not using in the Containers view or with
docker stop. Fewer running containers means less CPU and memory. - Lower the memory and CPU limits. Open Docker Desktop's Settings > Resources > Advanced and reduce the memory limit and CPU limit. Pick values that still leave your containers enough to run.
- Keep Resource Saver on. Resource Saver stops the Linux virtual machine when no containers are running. It is on by default; the timeout can be changed in Settings > Resources.
- Use Rosetta for Intel images. On Apple silicon, turn on Use Rosetta for x86_64/amd64 emulation on Apple Silicon if you run Intel images. Native arm64 images avoid emulation altogether.
- Stop it starting at login. In Settings > General, turn off Start Docker Desktop when you sign in to your computer and open it only when you need it.
When should you worry about Docker Desktop?
If the Mac shows high memory pressure while Docker runs, the memory limit is set too high for that Mac. Lower it before closing other apps.
Containers that restart in a loop keep CPU busy; docker ps -a shows their status and restart counts.
How do you check Docker Desktop in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type Docker Desktop in the search field. The Memory tab shows its Memory. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every Docker Desktop process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'Docker Desktop' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
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 about Docker Desktop
Why does Docker use memory when no containers are running?
The Linux virtual machine keeps running until Resource Saver stops it. With Resource Saver turned off, it stays up until you quit Docker Desktop.
How much memory should I give Docker Desktop?
Enough for the containers you run at once. The default is half of the Mac's memory; many projects run fine with less, and memory pressure in Activity Monitor shows whether the rest of the Mac is short.