Pool overlaps 🐳 Docker

Error response from daemon: Pool overlaps with other one on this address space

Docker tried to create a network whose subnet clashes with an existing Docker network (or a VPN/host route).

Seen on: Docker

Meaning

Each network gets a subnet from Docker’s default pools. Fixed subnets in Compose files, too many leftover networks, or a VPN using 172.x addresses cause overlaps — and can also make hosts on your LAN/VPN unreachable from containers.

Common causes

  • Two Compose projects define the same subnet
  • Old networks exhausted the default pool
  • VPN or corporate network uses the same range

⚡ Quick fix

  1. Remove unused networks: docker network prune
  2. Change or remove the subnet in docker-compose.yml
  3. Configure default-address-pools in daemon.json

Detailed fix by platform

Docker

  1. bash
    docker network prune
# /etc/docker/daemon.json
{ "default-address-pools": [{ "base": "10.210.0.0/16", "size": 24 }] }

How to diagnose

  1. Subnets — docker network inspect $(docker network ls -q) | grep Subnet
  2. Routes — ip route (VPN ranges)

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.