OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
apps-services medium common DISPUTE

Fix Docker "could not find an available, non-overlapping IPv4 address pool"

omarchyarchdocker
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

The moby source (daemon/libnetwork/ipamutils/utils.go) still defines the local default pools as 172.17 through 172.31 in /16 blocks plus 192.168.0.0/16 in /20 blocks, 31 networks, which matches the record's count and the Arch wiki's 172.17.0.0/12 table. The plain Arch JSON is the wiki's version verbatim. On this workstation /etc/docker/daemon.json is owned by omarchy-settings 4.0.4-1, unmodified, and identical to quattro's etc/docker/daemon.json, so the Omarchy JSON keeps every shipped key. 172.18.0.0/15 at size 24 gives 512 networks, stays clear of the 172.17.0.0/16 bip, and stays inside the 172.16.0.0/12 that both the allow-docker-dns ufw rules in install/config/firewall.sh and the ufw-docker after.rules cover. install/config/docker.sh confirms the user is not put in the docker group and the menu has Setup > Security > Sudoless Docker. Not exercised: restarting docker.

RISK

docker network prune deletes every network with no container attached, including ones a stopped project expects to reuse. Restarting docker.service stops all running containers. Existing networks keep their old subnets until recreated.

Symptom

docker compose up fails before any container starts:


failed to create network actualbudget_default: Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network

docker network ls shows a long list of <project>_default networks from old compose projects.

Cause

Every compose project creates its own bridge network, and Docker carves those from small default pools: 172.17.0.0/12 in /16 blocks and 192.168.0.0/16 in /20 blocks, which is only about 30 networks. Networks from projects you stopped testing are never removed, so the pools run dry.

Fix

Free what is unused. On Omarchy 4 your user is not in the docker group unless you opted in through Setup > Security > Sudoless Docker, so use sudo:


sudo docker network ls
sudo docker network prune          # removes networks no container uses
# or, in a project you are finished with:
sudo docker compose down

Then enlarge the pool so it stops recurring.

**Omarchy 4:** /etc/docker/daemon.json is owned by omarchy-settings and its dns and bip keys are what make container DNS work, so add the key and keep the rest. Keeping the pool inside 172.16.0.0/12 means the shipped allow-docker-dns ufw rule already covers it, and 172.18.0.0/15 at size 24 gives 512 networks without touching the 172.17.0.0/16 that bip pins to docker0:


{
    "log-driver": "json-file",
    "log-opts": { "max-size": "10m", "max-file": "5" },
    "dns": ["172.17.0.1"],
    "bip": "172.17.0.1/16",
    "default-address-pools": [
        { "base": "172.18.0.0/15", "size": 24 }
    ]
}

**Plain Arch:** the file usually does not exist. The Arch wiki's version shrinks both default pools to /24 blocks:


{
  "default-address-pools": [
    { "base": "172.17.0.0/12", "size": 24 },
    { "base": "192.168.0.0/16", "size": 24 }
  ]
}

Apply on either:


python3 -m json.tool /etc/docker/daemon.json
sudo systemctl restart docker.service

Verify

sudo docker network create pooltest && sudo docker network inspect pooltest --format '{{(index .IPAM.Config 0).Subnet}}' prints a /24 from the new pool, then sudo docker network rm pooltest. docker compose up creates its network.

Sources

docker-no-available-non-overlapping-address-pool