dosba

Hello everyone, I'm running into a persistent issue and I'm hoping someone can point me in the right direction. My Goal: I want to move a Docker container (Pi-hole) to its own dedicated physical network interface eth1) to resolve a MAC address conflict on br0. I've recently installed a additional PCIe networking card for future plans like OPNsense. But that's a problem for the future. The Problem: I have successfully created a new bridge br1) and assigned it to the physical interface eth1 in Settings → Network Settings. The Unraid host OS sees the bridge correctly. However, the Docker service does not recognize this new bridge. It is not available as an option in the Docker container's network settings (GUI), and trying to assign it via the CLI results in a "network not found" error. What I've already tried: * Rebooting the server multiple times. * Stopping the array and "refreshing" the network settings by hitting APPLY again. * Completely deleting the docker.img file and letting Unraid recreate it, then reinstalling the apps from "Previous Apps". * Removing the Tailscale plugin to rule out conflicts. The issue persists even after all these steps. It seems like the Docker service is not correctly picking up the network configuration from the host system. System Information: Here is the output of ip a, which shows that br0, br1, and br2 exist on the host: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 6: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether c4:62:37:05:af:f2 brd ff:ff:ff:ff:ff:ff inet6 fe80::c662:37ff:fe05:aff2/64 scope link proto kernel_ll valid_lft forever preferred_lft forever 7: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br1 state UP group default qlen 1000 link/ether c4:62:37:05:af:f3 brd ff:ff:ff:ff:ff:ff 8: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq master br2 state UP group default qlen 1000 link/ether 70:85:c2:a6:9e:fe brd ff:ff:ff:ff:ff:ff 18: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether c4:62:37:05:af:f2 brd ff:ff:ff:ff:ff:ff inet 192.168.178.63/24 metric 1 scope global br0 valid_lft forever preferred_lft forever inet6 fd39:1bd4:726b:0:c662:37ff:fe05:aff2/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 6798sec preferred_lft 3198sec inet6 2a02:3102:6990:6900:c662:37ff:fe05:aff2/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 6798sec preferred_lft 3198sec inet6 fe80::c662:37ff:fe05:aff2/64 scope link proto kernel_ll valid_lft forever preferred_lft forever 19: br1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether c4:62:37:05:af:f3 brd ff:ff:ff:ff:ff:ff 20: br2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 70:85:c2:a6:9e:fe brd ff:ff:ff:ff:ff:ff 21: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:3d:3e:21:e1 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever inet6 fd17::1/64 scope global nodad valid_lft forever preferred_lft forever --- Here is the output of docker network ls, which shows that Docker only recognizes br0: NETWORK ID NAME DRIVER SCOPE 1732e707fb33 br0 ipvlan local 3aefd366bc3b bridge bridge local 48581d845ce3 host host local b561e3aab1e3 none null local --- I have attached my full system diagnostics file to this post. Thank you in advance for any help or insights you can provide! homelab-diagnostics-20250806-2118.zip