Docker-mailman: ERROR: Pool overlaps with other one on this address space

Are you using 172.19.199.1/24 subnet for something else in your network?

The default compose file provided uses this subnet to create a bridge network and allocates static IPs to the containers.

If this subnet is already in use, you can just change it to a different subnet. You'd have to change
environment variables and other IPAddresses allocated to each container too.

See the docker-compose.yaml file in the root of the project.

Hi !

Thanks for the quick answer 👍

FTR I am using the docker-compose.yaml file at the root of the project

There's no other docker containers running on the host while I'm doing this test.

I changed the subnet to 172.20.199.1/24 and modified the other IP adresse accordingly and I still get the same error..

Not exactly sure about what is going on but this thread from docker might be relevant?

Hi !

Actually it seems that a simple sevirce docker restart solved the issue.

Sorry about that. Thanks for your help !

In case someone else is google'ing here: Even if the containers are down the networks are still persist. With no container running docker network prune did it. Guess restarting the service returns the same result.

I think the semantics depend on how you actually stop the containers, docker-compose stop actually only stops the containers, but, docker-compose down stops and remove the containers & network.

https://docs.docker.com/compose/reference/down/
https://docs.docker.com/compose/reference/stop/

Working when I delete the pool network

docker network ls
NETWORK ID          NAME                          DRIVER              SCOPE  
8518cc751c09        bridge                        bridge              local  
5ebc27713033       pool_network              bridge              local  
25ff8d61d971        host                          host                local  
85c5507b6e64        none                          null                local

remove the pool_network

docker network rm pool_network

İt was about the wrong ip address in compose.yml in my case

my case, I have to tun

docker-compose down
docker network prune

Then restart Docker service.

version: "3"

networks:
tut07-frontend:
driver: bridge
ipam:
driver: default
config:
- subnet: 172.10.1.0/24
tut07-backend:
driver: bridge
ipam:
driver: default
config:
- subnet: 172.10.2.0/23

services:
tut07-db:
build: ./db
command: --default-authentication-plugin=mysql_native_password
ports:
- 3306:3306
networks:
tut07-backend:
ipv4_address: 172.10.3.2
env_file:
- ./development.env
tut07-www:
build: ./www
ports:
- 8080:80
volumes:
- ./src:/var/www/html/
networks:
tut07-backend:
ipv4_address: 172.10.2.2
tut07-frontend:
ipv4_address: 172.10.1.2
depends_on:
- tut07-db
env_file:
- ./development.env

#

above is my docker compose yml file but i got the same error even i have change

docker network prune

In case someone else is google'ing here: Even if the containers are down the networks are still persist. With no container running docker network prune did it. Guess restarting the service returns the same result.

it´s worked for me. Thanks you.