adminmat Posted December 23, 2020 Share Posted December 23, 2020 I'm sure i have something configured wrong here but... When I reboot the OS (example to add new disk or OS upgrade) I have to cycle the Docker service off then on. If not my network settings for the Containers are incorrect. After a reboot of the unRAID OS if I try to start a container I get this error: I have the Containers set to br0 before the reboot: After reboot the "Update Container" / Edit page is set to "None" for Network Type and does not show an option for br0 until I go to Docker settings and cycle it off then on. (Enable Docker: No > Apply then Yes > Apply) Maybe this is expected behavior. I just want to make sure I'm not doing something wrong here. Quote Link to comment
Squid Posted December 23, 2020 Share Posted December 23, 2020 Post your diagnostics Quote Link to comment
adminmat Posted December 23, 2020 Author Share Posted December 23, 2020 thanks for taking a look tower-diagnostics-20201223-1546.zip Quote Link to comment
Squid Posted December 23, 2020 Share Posted December 23, 2020 Looks like a very slow network to initialize. Since duckDNS is running as host, set it to the first container in the list, then in advanced view, set a delay on it for say 20 seconds to see if it improves things. Quote Link to comment
adminmat Posted December 26, 2020 Author Share Posted December 26, 2020 I've kind of solved this by disabling Docker before a reboot. Which isn't often enough to be of concern. Quote Link to comment
Recommended Posts
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.