[6.9.2] Docker with multiple connected networks cannot start on reboot / docker daemon restart
Hello,
I'm currently using Home Assistant docker connected to two networks: one is custom created (using docker network create), the other one is br0 (my Lan network).
I found that if a second network is connected to the docker (using docker network connect), on unraid reboot or even just turning off and on the unraid docker daemon the container will not auto-start. When trying to start the container manually I get the error message "No such container."
The only way
Retest
Minor
A few days ago I had this issue as well, I spent a little time researching it.
Unraid re-creates the Docker networks on reboot (actually, the service script destroys them on stop then re-creates them on start, so this happens even if you just restart the docker service).
When the networks are re-created they get new network ids.
Problem is, the container config still references the old network ids (you can see this if you do a docker container inspect <container&g
