June 23, 20233 yr Hi all, recently I noticed my docker containers weren't auto-starting. I figured it might be a glitch in the 6.12.0 RCs, and didn't think much about it. But yesterday I noticed that my PiHole containers aren't starting even after I click "start all". Digging a little more, I found that they had lost their IP addresses, and that br0 wasn't listed in the available networks: I tried rebooting, and also following the docker network rebuild instructions in this thread, but neither helped. I'll attach my system diagnostics. I'll also attach my docker and network settings. Any help would be appreciated. Things I've done recently: installed various 6.12.0 RCs, installed a gluetun container to experiment with (which created a proxynet I think), booted the computer with the network cable unplugged. storage-diagnostics-20230623-0849.zip Edited June 24, 20233 yr by coppit Marked solved, added 6.12.0 to title
June 23, 20233 yr Solution br0 is up: br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.22.33.100 netmask 255.255.255.0 broadcast 10.22.33.255 Start by updating to v6.12.1 stable.
June 24, 20233 yr Author Updating to 6.12.1 brought br0 back. I guess I'll chalk this up to 6.12.0 RC weirdness.
December 18, 20232 yr Hi all, not sure what the fix was but I just upgraded to 6.12.6 2023-12-01 and have the same symptom: br0 gone. Anyone any clues? Or steps to rebuild it as originally intended?
December 19, 20232 yr Try disabling and re-enabling bridging, if it doesn't help post the diagnostics.
July 13, 20241 yr Toggling Enable Docker from Yes to No to Yes in Settings -> Docker worked worked for me. Edited July 13, 20241 yr by unraid33
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.