Goblin

I never got this fixed, so had to workaround by using a docker IP address to access the container from the host, and use spilt horizon DNS to decide which IP to return based on who was asking.

FYI - The reason why the Unraid host needed to be able to reach a container via br0 is because I run a docker registry in a container (on 192.168.0.130) and I have the Unraid host use that registry as well as other devices outside of Unraid using it too. All via a single domain, e.g. docker.mydomain.com -> 192.168.0.130 (container running the registry). What I'm doing at the moment to work around the Unraid host not being able to reach the container via br0 is using split horizon DNS for docker.mydomain.com so that the Unraid host receives the private docker network IP address of the registry container, whereas everybody else receives the br0 address (192.168.0.130). Not ideal, but is working for now. Given this workaround is working ok for me right now, I'll probably switch my br0 network back to ipvlan as I know thats more stable and recommended than macvlan.

Oh no, I lied. After an Unraid reboot, the host can no longer reach containers using their br0 IP address.

So, I just figured out that the update from 7.0.0 to 7.0.1 had switched my br0 network type from macvlan to ipvlan. By switching the type back to macvlan, the Unraid host can now reach containers via their br0 IP addresses.

Hi Jorge, I've attached a screenshot of the docker network ls command output: Which parts of the diagnostic zip should I attach? I'd need to go through and censor parts of it as there are a lot of personal details in path names, etc. (I know, bad practice) that show up a fair bit. Thanks, Goblin.

Forgot to add, this is what my routing table looks like in Unraid Network Settings:

Hi folks, Hope somebody can point me in the right direction. I've been running Unraid for a year or so and have never had any issues after updating to the latest versions. However since updating from 7.0.0 to 7.0.1, I've found that the Unraid host is not able to find a route to docker containers that use the br0 network. Other devices on the network can access those containers, and even other containers can access those containers via their br0 IP address, so it's only the Unraid host > docker container via br0 that can't communicate where it previously could. For example: Unraid host has IP address 192.168.0.120 A docker container uses the br0 network and has IP address 192.168.0.130 Devices on the wider network can ping the container. But the Unraid host can't. I'll attach a couple of screenshots below if they help. Thanks folks. Unraid docker settings: Ping from Unraid host to docker container via br0 address: