DougP

I found the solution to this particular problem: I had to enable "Host access to custom networks" in the Advanced Docker settings and enable the desired Subnet.

I ended up wiping all of the network settings by deleting the network configuration files and starting from scratch. That worked through a couple of reboot cycles but, unfortunately, the problem has resurfaced. The two networks I'm having trouble with are on USB3 Ethernet Dongles which, I expect, could be part of the problem. Unfortunately all of my PCIe slots are already being used and USB3 is the only way I can get onto these networks..

br2 is the network I'm trying to attach the docker container to. This would be subnet 172.17.0.0/24. I currently have no docker containers attached to that bridge (since it's not an option). I assume that the 172.17.0.0/16 route connected to "docker0" is illegitimate so I tried to delete it - to no avail; the delete button asks me to confirm but never actually removes the route. I suspect this might help point towards a solution. EDIT: I deleted the 172.7.0.0/16 route using the command line: ip route del 172.17.0.0/16 The route was removed from the table but it hasn't helped me apply br2 to a docker container.

I am trying to assign a Unifi Controller docker container to an external network so it can manage our Access Points. The NIC is attached to the external network and was able to receive an IP address via DHCP. The interface (br2, 172.17.0.0/24) is enabled in the Docker settings page. Unfortunately, I've seen two issues: At boot-time I see an error message that says "br2 not found" and br2 isn't available in the Docker settings for Docker images: I'm at a loss here. What do I need to do to enable br2 on my Docker images?