What is com.docker.backend, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Role and account taken from Docker's documentation; Docker Desktop is not installed on the Mac used for checking.
com.docker.backend is the backend process of Docker Desktop; it runs as your user and starts the helper processes that run Docker's Linux virtual machine and connect it to the Mac. It is busy while containers are running or images are being built, and quiet when Docker is idle. It is safe; limit Docker's CPU and memory in Docker Desktop's Resources settings or quit Docker Desktop when you do not need it.
com.docker.backend at a glance
| com.docker.backend | |
|---|---|
| Made by | Docker, Inc. (part of Docker Desktop) |
| Type | App background process |
| Runs as | your user |
| Can you quit it? | Quit Docker Desktop instead of this one process; Docker Desktop stops its backend and virtual machine when it quits. |
What is com.docker.backend?
Docker Desktop for Mac runs containers inside a lightweight Linux virtual machine that Docker manages, because containers need a Linux kernel. com.docker.backend is the Docker Desktop process that sits between the Docker Desktop app, that virtual machine and the Mac. Docker's documentation says it uses an internal socket in ~/Library/Containers/com.docker.docker/Data/ to fork and execute helper processes as part of running Docker Desktop.
Docker documents that this process does not run as root and has no elevated privileges. Work that does need administrator rights goes through a separate privileged helper, com.docker.vmnetd, which launchd starts and which the backend talks to over /var/run/com.docker.vmnetd.sock.
Is com.docker.backend safe?
Yes. It is part of Docker Desktop, installed with /Applications/Docker.app. If you never installed Docker Desktop and see this process, check the Applications folder; another tool may have installed it.
Why does com.docker.backend use so much CPU, disk and memory?
- Containers doing work. Everything a container does, from a database to a web server, runs in Docker's Linux virtual machine. The more work containers do, the more the processes Docker Desktop starts have to do on the Mac.
- Building images.
docker buildcompiles and copies files inside the virtual machine, which is CPU-heavy while it runs. Images for a different CPU architecture are slower because they are emulated. - Sharing files with containers. Bind mounts make folders on the Mac visible inside containers. Docker Desktop shares them with VirtioFS by default on the Apple Virtualization framework; projects with many files that change often create a lot of file traffic.
- The virtual machine's memory. Docker Desktop gives its Linux virtual machine a memory limit that defaults to 50% of the Mac's memory, plus a 1 GB swap file. While the virtual machine runs, that memory is in use.
How much CPU is normal for com.docker.backend?
With no containers running, Docker Desktop's processes are typically close to idle, and Resource Saver stops the virtual machine after a few minutes. With containers running, CPU tracks what the containers are doing.
Memory use in the hundreds of megabytes to several gigabytes is normal while the virtual machine runs, up to the memory limit set in Docker Desktop.
How do you stop com.docker.backend from using so much CPU?
- Stop containers you are not using. Run
docker psto see running containers anddocker stop <name>to stop ones you do not need. Docker Desktop's Containers view does the same. - Keep Resource Saver on. Resource Saver, on by default, stops the Linux virtual machine when no containers have run for a set time (5 minutes by default). You can check it in Docker Desktop's Settings > Resources.
- Lower the CPU and memory limits. In Settings > Resources > Advanced, reduce the CPU limit and memory limit given to Docker. Containers get less, and the Mac keeps more for other apps.
- Use VirtioFS for file sharing. In the file sharing settings, VirtioFS is the default and Docker's recommended implementation for speed with the Apple Virtualization framework.
- Quit Docker Desktop. Quit Docker Desktop from its menu bar icon when you are not working with containers. com.docker.backend and the virtual machine stop with it.
When should you worry about com.docker.backend?
Look closer if com.docker.backend stays busy with no containers running and no build in progress; check docker ps -a for containers that keep restarting.
A com.docker.backend process on a Mac where nobody installed Docker Desktop is worth checking in the Applications folder.
How do you check com.docker.backend in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type com.docker.backend in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every com.docker.backend 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 'com.docker.backend' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
How can Thrum help with com.docker.backend?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when com.docker.backend is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click com.docker.backend 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 com.docker.backend
Does com.docker.backend run as root?
No. Docker's documentation says Docker Desktop for Mac runs as an unprivileged user, and only the separate com.docker.vmnetd helper runs with administrator rights.
Why does Docker use so much memory even with small containers?
The memory limit belongs to the whole Linux virtual machine, which defaults to half of the Mac's memory. Lower it in Settings > Resources if your containers need less.