- Minor
I've had this issue on the 7.2 betas and at that time rolled back to 7.1.4 to workaround. Now that 7.2 is now released, I upgraded on day 1 (last week); no issues with br0 missing from docker networks on upgrade. However this morning I needed to reboot the server and struck this issue when one of my containers using br0 network couldn't start. Investigated and found br0 was missing from docker network ls. After multiple reboots, disabling docker service and re-enabling etc.., I was unable to bring back the br0 docker network automatically. Interesting, when i switched my network config from ipv4+ipv6 to ipv4 only that brought back the br0 docker network. However one of my containers (matter-server) requires ipv6 enabled so ipv4 only was not an option.
In the logs i can see these events when working successfully:Nov 2 08:10:02 apollo rc.docker: Processing... br0
Nov 2 08:10:02 apollo rc.docker: created network ipvlan br0 with subnets: 10.0.0.0/24; fd69:fb66:5f3:6f4c::/64;
Compared to when not creating br0 docker network:Nov 2 08:59:33 apollo rc.docker: Processing... br0
Nov 2 08:59:33 apollo root: multiple overlapping subnet configuration is not supported
To remediate it seems that if manually create the docker network br0, it works without issue. This is how I am working around the issue for now, just means I need to execute on every reboot.docker network create \
-d ipvlan \
--subnet=10.0.0.0/24 \
--gateway=10.0.0.1 \
--ipv6 \
--subnet=fd69:fb66:5f3:6f4c::/64 \
-o parent=br0 \
--ipam-opt AuxiliaryAddresses=server=10.0.0.100 \
br0
I've attached the diagnostics.