CrimsonTyphoon Posted September 23, 2018 Share Posted September 23, 2018 I posted about this issue in the main 6.6.0 release thread (link), but wanted to make a separate thread specifically on this issue. On 6.5.3, I have 3 separate docker networks: br0: 192.168.20.0/24. Gateway 192.168.20.1 br1.10: 192.168.10.0/24. Gateway 192.168.10.1. (VLAN 10) br1.20: 192.168.20.0/24. Gateway 192.168.20.254 (VLAN 20) Note: br0 and br1.20 are in the same subnet, but have different gateways. I do this so dockers in br1.20 can connect to both the Unraid host, and dockers in all subnets (circumventing macvlan from blocking the connection between docker and host) All 3 networks have no DHCP pool, i manually set them for my docker containers. Now the problem. When I upgraded to 6.6.0, I could still see my 3 docker networks in docker settings, but I could no not select br1.20 in Update Container, under Network Type, it is simply not listed. Can someone let me know how I can do this, preferably through the GUI? Quote Link to comment
bonienl Posted September 23, 2018 Share Posted September 23, 2018 Can you post a screenshot of your Docker settings page (enable advanced view) And what is the output of docker network ls Quote Link to comment
CrimsonTyphoon Posted September 24, 2018 Author Share Posted September 24, 2018 10 hours ago, bonienl said: Can you post a screenshot of your Docker settings page (enable advanced view) And what is the output of docker network ls Here are my settings under 6.5.3 / 6.6.0 IPv4 custom network on interface br0: Subnet: 192.168.20.0/24 Gateway: 192.168.20.1 DHCP pool: not set IPv4 custom network on interface br1.10: Subnet: 192.168.10.0/24 Gateway: 192.168.10.1 DHCP pool: not set IPv4 custom network on interface br1.20: Subnet: 192.168.20.0/24 Gateway: 192.168.20.254 DHCP pool: not set NETWORK ID NAME DRIVER SCOPE b9b4178725d9 br0 macvlan local 0b839cad0823 br1.10 macvlan local 37bff31973a8 br1.20 macvlan local e1ef694e36c7 bridge bridge local f9bfd58f90c4 host host local 7759dbce282b none null local Under 6.5.3, I can set the network type to any of the networks when adding/updating a container. In 6..6.0, I can pick everything except br1.20 Quote Link to comment
ken-ji Posted September 24, 2018 Share Posted September 24, 2018 I wonder if the limitation you are seeing is caused by having "two" subnets with the same addressing range but different gateways to work around docker not even allowing the docker network to be defined in more than one NIC. Is that it @bonienl? Quote Link to comment
bonienl Posted September 24, 2018 Share Posted September 24, 2018 When no DHCP pool is specified, docker takes the complete subnet as pool. This creates an overlap between interface br0 and br1.20. Use different DHCP pools and try again. 1 Quote Link to comment
CrimsonTyphoon Posted September 25, 2018 Author Share Posted September 25, 2018 18 hours ago, bonienl said: When no DHCP pool is specified, docker takes the complete subnet as pool. This creates an overlap between interface br0 and br1.20. Use different DHCP pools and try again. That was it, thank you! Quote Link to comment
pzg417 Posted March 15, 2022 Share Posted March 15, 2022 On 9/25/2018 at 10:07 AM, CrimsonTyphoon said: That was it, thank you! Could you please tell me how to change the DHCP pool settings? I have exactly the same problem. Quote Link to comment
Squid Posted March 15, 2022 Share Posted March 15, 2022 Settings - Docker with the service stopped. Switch to Advanced view Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.