Suddenly when I want to create a network (either with docker network create test or with a docker compose file and an implicit network) I get the error mentioned in the title. It seems to imply that I run a lot of networks but docker network ls shows only what seems to be the default networks: bridg…

I think my problem was that the company VPN’s routes were excluded from the available network pool.

Error response from daemon: all predefined address pools have been fully subnetted

esbenboye (Esbenboye) June 20, 2025, 4:45am 4

To follow up on this and help any one who might not so Docker-savy; If you run the command docker network prune it will delete all networks currently not used by any container.

Topic		Replies	Views
Failed to create network project_default: Error response from daemon: all predefined address pools have been fully subnetted General	7	3503	April 29, 2025
Error: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network General	14	12035	January 24, 2024
Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network General	1	17999	April 1, 2020
Cannot create network (br-....) conflicts with (br-...): networks have overlapping IPv4 Compose	1	2579	March 11, 2021
Docker compose network General docker , docker-compose , networking	3	261	December 2, 2024

Error response from daemon: all predefined address pools have been fully subnetted

Related topics