docker-mailman: ERROR: Pool overlaps with other one on this address space
Hi
Thanks for this projet ! Installing Mailman3 is tricky and I hope your docker images will help
However I’m getting an error at the early stage:
$ docker-compose up
Creating network "dockermailman_mailman" with driver "bridge"
ERROR: Pool overlaps with other one on this address space
the host is a regular Linux box:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
$ uname -a
Linux Hammer 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
The docker version seems up to date
docker version
Client:
Version: 17.05.0-ce
API version: 1.29
Go version: go1.7.5
Git commit: 89658be
Built: Thu May 4 22:10:54 2017
OS/Arch: linux/amd64
Server:
Version: 17.05.0-ce
API version: 1.29 (minimum version 1.12)
Go version: go1.7.5
Git commit: 89658be
Built: Thu May 4 22:10:54 2017
OS/Arch: linux/amd64
Experimental: false
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 9
- Comments: 27 (3 by maintainers)
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.Hi !
Actually it seems that a simple
sevirce docker restart
solved the issue.Sorry about that. Thanks for your help !
my case, I have to tun
Then restart Docker service.
Working when I delete the pool network
remove the pool_network
docker network rm pool_network
docker network prune
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/
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.
Change your subnet 172.* to 192.*
it´s worked for me. Thanks you.
In case you are configuring docker networks with bridge mode and in case you are assigning pool of addresses, make sure each stack has a unique subnet, in my case I had two docker-compose files using the same subnet:
In my case, subnet 192.168.175.0/24 was used by two stacks, hence the error.
Not exactly sure about what is going on but this thread from docker might be relevant?
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…