Docker making your Mac hot? How to cool it down

Docker on a Mac means a Linux virtual machine running next to everything else. Left unchecked, it can keep the chip busy all day.

By Andrew Wilson · Updated 2026-11-02

Short answerDocker Desktop runs your containers inside a Linux virtual machine, so busy containers, file-watching across the Mac/VM boundary and x86 images running under emulation all heat the Mac. To cool it: cap the CPUs and memory Docker may use (Settings → Resources), keep Resource Saver on so the VM stops when no containers run, use arm64 images instead of amd64 ones, stop containers you aren't using, and limit what dev containers watch for file changes.

WhoIsCooking panel showing the Mac's chip temperature and the apps heating it, busiest first — WhoIsCooking shows the chip temperature and which apps are heating the Mac, busiest first, with a one-click Cool down.

Why Docker heats a Mac

It's a VM. On macOS, containers run inside a Linux virtual machine. Everything the containers do is CPU work on your Mac.
Idle containers aren't always idle. Databases, queues, dev servers with hot reload and health checks keep doing small amounts of work forever.
File watching. Dev setups that bind-mount your project and watch files (webpack, nodemon, Next.js dev) generate a stream of file events between the Mac and the VM.
Emulation. Running linux/amd64 images on Apple Silicon means translating x86 code, which costs far more CPU than native arm64 images.

Fixes, in order

See what's busy: docker stats shows CPU per container. Stop the ones you don't need: docker compose stop <service>.
Cap resources: Docker Desktop → Settings → Resources. Give it fewer CPUs (for example half your cores) and only the memory it needs. Containers will run a bit slower but can't take over the Mac.
Keep Resource Saver on. Docker's docs say it stops the Linux VM when no containers have run for a while (5 minutes by default), which cuts CPU and memory use on the Mac.
Use arm64 images. Check with docker image inspect <image> --format '{{.Architecture}}'. Most popular images publish arm64 versions; rebuild your own images for arm64.
Tame file watchers: ignore node_modules, build output and .git in your watcher config, or run the dev server on the Mac and only databases in Docker.
Quit Docker Desktop when you aren't using it at all.

Running builds in Docker for a long time?

Long image builds and test suites in containers are the same kind of heavy load as any build. The general advice in keeping a Mac cool during heavy work applies: one heavy job at a time, a stand, and fewer parallel jobs.

Frequently asked questions

Why is com.docker.virtualization or qemu using so much CPU?

That's the Docker VM or the x86 emulator doing the containers' work. Find the busy container with docker stats, and switch amd64 images to arm64 where you can.

Does Docker Desktop use CPU when no containers are running?

Very little with Resource Saver on, which stops the VM after a few idle minutes. With it off, the VM keeps running.

How many CPUs should I give Docker on a MacBook?

Start with about half your cores. Raise it only if your containers are noticeably too slow.