---
title: "com.docker.backend: why Docker Desktop uses the network on a Mac, and whether to block it · Kilobat"
url: "https://kilobat.app/processes/docker-desktop"
description: "com.docker.backend is Docker Desktop's network proxy on a Mac. Why container traffic appears under it, how port forwarding works, and what breaks if you block it."
---

# What is com.docker.backend?

`com.docker.backend` is part of Docker Desktop. Docker says that all outbound container traffic comes from this process, so every container's connection shows under its name.

**Fix this with your agent**Copies a prompt for Claude Code, Codex or any agent that can use Terminal.

I want to know what com.docker.backend is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/docker-desktop.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Process: `com.docker.backend` · Also seen as: `Docker Desktop`, `vpnkit`, `com.docker.vpnkit` · Made by Docker · Applies to: Docker Desktop on macOS 14 Sonoma and later. Checked on 7 November 2026 against Docker's documentation. · Checked: 7 November 2026

## Short answer

Docker Desktop's backend. All outbound traffic from your containers appears as this process, and it listens on the host ports that you publish.

Block with care

Blocking the backend cuts off all container internet access and image pulls. Docker commands that need a registry fail.

Path

`/Applications/Docker.app/Contents/MacOS/com.docker.backend`

## What it is

Docker's networking page says that the backend acts as the network proxy between macOS and the Linux virtual machine. It also handles Docker API calls, port forwarding and proxy settings.

Docker states that all outbound container network traffic originates from the `com.docker.backend` process.

A container's network adapter connects to a bridge inside the virtual machine. Docker says that traffic is NATed and then crosses to the host through a shared-memory channel, not a normal virtual network interface.

The backend then opens ordinary TCP and IP connections on the Mac. A firewall rule for the backend therefore applies to the virtual machine's networking.

When you publish a port with `-p`, the backend listens on that port on the Mac. By default it binds to `0.0.0.0`. Docker says that you can limit it to `127.0.0.1` or one adapter.

## Why it uses the network

- **Image pulls.** `docker pull` and builds download image layers from registries. Docker says that the Desktop proxy or the Containers proxy governs this.
- **Container traffic.** Whatever your containers connect to, such as package mirrors, APIs and databases, shows as the backend's traffic.
- **Published ports.** A published port makes the backend listen on the Mac and forward connections into the virtual machine.
- **Proxy handling.** Docker says that both proxy types follow the system or manual proxy settings.

## How much is normal

Traffic follows what your containers do. An idle Docker Desktop with no running containers should send little.

Many short connections to different hosts are normal when a container installs packages or runs tests.

Connections to the Mac from other devices appear only if you published a port on all addresses.

## When it uses a lot, and why

- **Large image pulls.** A pull of a large image downloads every layer that you do not already have.
- **A build.** Builds fetch base images and dependencies, and may repeat when the cache does not apply.
- **A container that syncs or downloads.** A container that runs a download job, a mirror or a backup sends and receives as much as any app would.

## Is it safe to block?

Block with care

Blocking the backend cuts off all container internet access and image pulls. Docker commands that need a registry fail.

What breaks if you block it

- Containers cannot reach the internet, because their traffic goes through this process.
- Image pulls and builds that fetch from registries fail.
- Published ports stop accepting connections from outside the virtual machine.

Blocking means a firewall rule that refuses its connections. Don’t quit or disable a macOS process to save data: macOS starts it again, and other features depend on it.

## Reduce its use

1. To limit who can reach a published port, bind it to localhost. Use the form `-p 127.0.0.1:8080:80`.
2. Docker says that you can also make localhost the default binding in Docker Desktop's network settings.
3. Pull large images on a network that has room for them. Pull images before you travel.

## See how much it uses

1. Open Activity Monitor and search for `docker`. The Network tab shows the backend's bytes sent and received.

## With Kilobat

1. In the Kilobat app list, search for `com.docker.backend`. Its row shows the live rate and the hosts that it talks to.
2. Ask the same question in Terminal.

   ```
   kilobat explain com.docker.backend
   ```

The live view and the explanations are free. History in the app needs Kilobat Pro. Blocking needs Pro and the network filter: see the [network filter](https://kilobat.app/docs/blocking#filtering), [Protection](https://kilobat.app/docs/blocking#protection) and the [hotspot data saver](https://kilobat.app/save-hotspot-data).

## What isn’t documented

Docker's networking page does not name the hosts that Docker Desktop itself contacts, such as for updates or sign-in. This entry does not list any.

The page does not describe `vpnkit` on a Mac. It is listed as an alias only because it is a common name for Docker's network layer.

## Questions

**Why does every container connection show as com.docker.backend?**

Docker says that all outbound container traffic originates from that process. The Mac does not see the container's own address.

**Can other devices reach my published ports?**

By default the backend binds them to `0.0.0.0`, so yes. Docker says that you can bind to `127.0.0.1` instead.

**Does Docker Desktop work with a proxy?**

Yes. Docker says that both its Desktop proxy and Containers proxy honour system or manual proxy settings. NTLM and Kerberos are not supported natively on Mac.

## Sources

- [Docker Docs: Networking on Docker Desktop](https://docs.docker.com/desktop/features/networking/)
- [Kilobat docs: Connections](https://kilobat.app/docs)

Checked on 7 November 2026.

## Related

- [node](https://kilobat.app/processes/node): The Node.js runtime, not part of macOS. It connects only when a script asks, such as npm installing packages, a dev server, an AI agent or an MCP server.
