Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Option to automatically reboot Ubuntu for security updates

  • Staff

    The base image is on Bionic Beaver which is actually 18.04 LTS
    There is no technical reason to have the base image be the same Ubuntu version or even the same Linux distribution as the host system.

    Ubuntu 20.04 support will come soon for the host system, but the base image will remain on 18.04 for some time, since changing that requires retesting and fixing all app packages for no real reason at the moment.

    The most important aspect is that the versions are still supported 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.

  • @nebulon and @girish somehow this change (or something else) made the reboot of my 3 cloudron servers superfast!

    Before it took at least 4-6 minutes and today everything (all services and apps) are up again within 1 minute!!!!

    Good job!!


  • @imc67 Same here. Was really fast tonight for security updates.

  • Mine was really noticable faster too. Running Ubuntu 18.04 OS here.
    Reboot and apps up and running in less than a minute. Like 40 to 45 seconds in total.

    Keep up the good work Cloudron staff πŸ‘ πŸ‘

  • 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!


  • Same here, less than a minute now. Still looking forward to live patches. But I reboot a lot to change the way apphealthmonitor.js works (making it more accurate) and I need to reboot after every change so this is just a godsend. πŸŽ‰

  • Guess that β€œsync” was the problem then, though weird if it’s been in there for years already without issues. Maybe something just incompatible after certain updates were applied which caused sync to take so long.

  • @DanTheMan
    Likely due to improvements in 18.04.4 and above.

    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:

  • @robi Interesting feature. Could save development time. Thanks!

Log in to reply