Recommendations for rebooting container host #5185
-
|
Say I need to reboot my container host running AIO (eg: for OS updates). Should I log into the AIO interface and manually stop all the containers, then stop the master container on the commandline, then reboot? Or is it safe to just reboot the system and let Docker pull the containers down and automatically restart them all on reboot? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 18 replies
-
|
Hi,
Yes, this is the idea. |
Beta Was this translation helpful? Give feedback.
-
|
I think there is not just a lack of clear documentation but a functional deficit – whenever I shutdown the host system or the docker daemon without stopping the non-MC containers through AIO interface something goes wrong. Mostly, the Nextcloud container doesn't start again after and I have to rebuild it. I tried to automate the AIO-shutdown with system.d (cf few comments below), but this doesn't work either. So the dependency approach via yaml sounds interesting. Any ideas on how to accomplish this? Seems difficult, as the yaml just defines the MC and "doesn't know" the other containers, which are instantiated by the MC. |
Beta Was this translation helpful? Give feedback.
-
Indeed it would be more a hack than anything else - even if it works :-D I think that most users would expect the whole stack to be shut down cleanly and automatically when the MC is stopped, contrary to what happens atm, but maybe that precludes some interesting scenarios, such as hot-upgrading the MC without disruption to the NC application? In any case, having a concise one-liner command to stop both the MC and the dependent containers is clearly a need felt by many users... |
Beta Was this translation helpful? Give feedback.
-
Thinking more about this, it should be doable to achieve the best of both worlds with the following workflow:
@szaimen wdyt? |
Beta Was this translation helpful? Give feedback.
-
|
I dont think we should go this way. The docker daemon should handle the stopping for us correctly. In any way, feel free to open a feature request for this here: https://github.com/nextcloud/all-in-one/discussions/new?category=ideas |
Beta Was this translation helpful? Give feedback.
-
|
See request at #8321. It is a different question as to whether docker daemon should wait for all (user) containers to gracefully stop when it is terminated. I guess we need both approaches. |
Beta Was this translation helpful? Give feedback.
-
|
Many thanks! |
Beta Was this translation helpful? Give feedback.
-
|
@szaimen Is this due to some misconfiguration on my side? I am looking for a simple, automated way to do maintanence on the host OS which would require a safe method to stop Nextcloud beforehand. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
So is running this script better than to just reboot the system and let Docker pull the containers down and automatically restart them all on reboot? |
Beta Was this translation helpful? Give feedback.
-
|
For starting you need to run the script on boot with START_CONTAINERS=1 |
Beta Was this translation helpful? Give feedback.
-
|
My aim is to stop AIO containers when the OS shutdown (i.e. OS receives shutdown signal from Hypervisor). |
Beta Was this translation helpful? Give feedback.
-
|
Hm... usually containers should be automatically stopped together with the host OS by the docker daemon... |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, this does not work reliably – docker daemon gives containers 10 sec to shutdown, which seems to be insufficient for Nextcloud AIO. Thus, the Nextcloud container is stopped ungracefully and must be recreated after restart. |
Beta Was this translation helpful? Give feedback.
-
|
I just created anothed guide. Can you check it out? |
Beta Was this translation helpful? Give feedback.
Hi,
Yes, this is the idea.