January 12, 20233 yr I have my main NIC eth0 for Unraid, SMB stuff like that. That NIC runs on the primary network, 200.x. I also have a second NIC eth1 in the server that I had purposed for Docker containers which runs on a different network, 202.x I have been fighting with my Unifi controller reporting multiple clients with the same IP and other nonsense and have a ticket open with them but I happened across something, just now. Docker containers that are on the bridge network are accessible from both NIC's! But in the network settings eth0 is the only member of br0. And eth1 is not bridged at all.
January 12, 20233 yr Author I've been playing around with this trying to figure out what's going on and it doesn't make sense to me....yet. I turned off bridging on both nic's and reassigned containers to networks. Either the default bridge or host. As before, all containers on the host network (eth0) can still be accessed from the IP address assigned to eth1 using their mapped port numbers. I then enabled bridging on eth1 (only) and again, assigned networks to containers. STILL, all host (eth0) containers can be access by the eth1 IP address. sidenote: Why is the br1 listed in the Docker networks using the IPVLan driver when it is supposed to be a bridge network? root@KNOXX:~# docker network ls NETWORK ID NAME DRIVER SCOPE a84669bab87f br1 ipvlan local 11f039ac639f bridge bridge local f41bc922a522 host host local e540bdf2755b none null local
January 12, 20233 yr Community Expert Makes sense that containers on host network would be reachable from any interface the host is reachable through.
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.