Option to automatically reboot Ubuntu for security updates
-
@nebulon So it was completely the other way around. You're updating the host version (what Cloudron runs on) to 20.04 (Focal), but leaving the DOCKERIMAGE
FROM
base version at 18.04 (Bionic) until at least security patch support stops coming out for it. Did I get that correct this time?Sorry, new to the Ubuntu world.
-
-
Wow. π€―
It's WAY faster now.
Like, lightning fast.
I just did a reboot to finish a Ubuntu security update and everything was back up and running in less than 60 seconds.
I almost couldn't believe it!
Thanks!
-
@DanTheMan
Likely due to improvements in 18.04.4 and above.@Lonk
To avoid having to reboot the box, you can run your tests in a docker container using the sysbox-runc for full OS (machine image) capability in a docker container.Then just reboot the sysbox container.
See requirements: https://github.com/nestybox/sysbox-ee/blob/master/docs/distro-compat.md -
Yep. For those cases it shouldn't be too bad: The fixed timeslots/dates can be communicated/planned accordingly and if it's on demand and no admin is available, the users can get told that they should be worried only if downtime is >1h or something like that. That's at least better than no patched server and in worst case coming home and finding a disaster .
-
-
@nebulon just for information - livepatch doesn't mean you don't have to reboot - it just lets you postpone that moment as convenient.
For
sync
- a good practice on old good *nix is to issuesync
twice before reboot - to make sure the buffers dumped for sure.On the reboot automation using third-party apps - it's doable; everything is, but why, if you can just add it inside of the system?