The upgrade went smoothly with the exception of a custom docker network I have.

I have bridging on my main NIC enabled:

I have a few custom VLANs enabled:

These custom networks are visible by the Docker tab:

But Docker20 the one I really need to work is not seen by the docker subsystem:

99% of my docker containers sit in that VLAN, and any of the ones that are assigned to Docker 20 wont start, however the few that are on Vlan30 or 50, work as intended.

Trying to re-assign the Docker20 custom network it doesn't show up in the drop down.

I have deleted the vlan, re-added it, and tried to manually add it via portainer, with no success.

In portainer when I try and add the macvlan driver based network, it gets created by the driver ends up false, even though I selected on macvlan:

Lastly when I try and create it manually like so:

It works, and the dockers start. However disabling docker the service, and restarting it, the docker20 network dissapears.

I use this same network with a VM, and that VM's network access works, while the docker's does not.

What's going on on how do I fix this ?

Edited August 17, 2025Aug 17 by bobo89
additional info

br0.20 has an invalid dhcp pool mask, most likely should be 10.10.20.128/25
Recent releases of Unraid have become more strict around correctness of docker network settings, which is why it might have worked in the past.

10 hours ago, tjb_altf4 said:

br0.20 has an invalid dhcp pool mask, most likely should be 10.10.20.128/25
Recent releases of Unraid have become more strict around correctness of docker network settings, which is why it might have worked in the past.

Very subtle, but that was it ,thanks!

Maybe a feature request to have some client side verification there, as there wasn't anything obviously wrong when setting the CIDR incorrectly.