- Annoyance
I had a an unraid server that was running with no issues. I changed the subnet of my network (on my router) from 192.168.1.0 -> 192.168.37.0. Unraid itself had no issues, it was able to pick up the new settings. For my docker containers, I restarted the docker service and that came back with no issues either. I never restarted the entire server as everything seemed to be working until I tried to deploy a pi-hole docker. Pihole requires br0 so that it gets it's own up address, but in the docker tab, when trying to make a new container with br0 network type, the subnet listed was still 192.168.1.0 instead of the new x.x.37.0 subnet.
The docker settings (capture1.png) show that docker had the correct network settings. Capture2.png shows that unraid itself had the correct settings. In the console, ifconfig also showed that br0 had the correct network settings. However, the docker creation tab was still showing the old settings. Only way to fix this was to restart the server, but that shouldn't be needed since both unraid and docker had the correct IPs. There is something specific about the unraid docker creation GUI that did not update correctly and required a full restart (capture3.png shows the correct IP now, because I didn't screenshot the before when it was 192.168.1.0).
When trying to deploy a container, it was giving errors saying that the IP is not in the subnet range so no containers with br0 networking could be deployed until it was fixed with a full reset. Even without specifying a fixed IP, it was trying to set something on the wrong subnet and also didn't work.
