July 14, 20205 yr In syslog ... ' rc.docker: Error response from daemon: Pool overlaps with other one on this address space' Seen it a few times recently.
July 14, 20205 yr In syslog ... 'rc.docker: Error response from daemon: Pool overlaps with other one on this address space' Seen it a few times recently.Check at Settings -> Docker -> upper right switch to advanced view What Networks are set?Seems like one is overlapping maybe a Subnet typo or using a Subnet like the standard 172 Network.Gesendet von meinem Pixel 3a XL mit Tapatalk
July 14, 20205 yr Author I only have Maria and nextcloud dockers installed as preconfigured.Sent from my CLT-L09 using Tapatalk
July 15, 20205 yr I only have Maria and nextcloud dockers installed as preconfigured.Sent from my CLT-L09 using TapatalkSounds good, and what networks did you configure? Did you run at some point 'docker network create'? As I mentioned before this will setup a network using the 172 as the first octet for the Network Subnet.
July 15, 20205 yr Author They are using 172.17.0.2 & 3 respectively. No command line input at all. In bridge mode. Sent from my CLT-L09 using Tapatalk
July 15, 20205 yr They are using 172.17.0.2 & 3 respectively. No command line input at all. In bridge mode. Sent from my CLT-L09 using TapatalkDo they only use 172.17.0.2? Or is it set like:172.17.0.2:80 192.168.1.2:80You can have a look in the Docker Tab.But as I mentioned before please have a look at the advanced docker settings if there are more than one network set within the same Subnet, there is your Problem.
July 15, 20205 yr Author Where are the advanced docker settings? Can't see them under advanced view on the dockers page itself? And yes, there is a :xxx.xxx.xxx. type entry alongside.Sent from my CLT-L09 using Tapatalk
July 15, 20205 yr Author Ok ... i've found them and my br2/br3 look like this IPv4 custom network on interface br2: Subnet: 192.168.2.0/24 Gateway: DHCP pool: not set IPv4 custom network on interface br3: Subnet: 192.168.2.0/24 Gateway: DHCP pool: not set Subnet: 192.168.1.0/24 Gateway: 192.168.1.1 DHCP pool: not set Could this be the cause and nothing to do with the existing dockers? Edited July 15, 20205 yr by superloopy1
July 16, 20205 yr Ok ... i've found them and my br2/br3 look like this IPv4 custom network on interface br2: Subnet: 192.168.2.0/24 Gateway: DHCP pool: not set IPv4 custom network on interface br3: Subnet: 192.168.2.0/24 Gateway: DHCP pool: not set Subnet: 192.168.1.0/24 Gateway: 192.168.1.1 DHCP pool: not set Could this be the cause and nothing to do with the existing dockers? Exactly. Just remove one of the Cables, if possible, and try again. Or stop all containers go into the docker settings and remove one of them by deselect them.
July 16, 20205 yr Author So ... there's a conflict somewhere? What needs to change? Do I need a new address for br3? None of these have a cable attachment or any dockers using the range yet.Sent from my CLT-L09 using Tapatalk
Archived
This topic is now archived and is closed to further replies.