Updating Silverblue on Shutdown

Ask Fedora
, ,
1

I am currently using Ubuntu 24.04 and looking to migrate to Silverblue 43 (probably the Budgie flavour as I currently use Ubuntu Mate) - I currently have Silverblue 43/Budgie running in a vm. On my Ubuntu system I have a script that runs* when I close down my pc. Essentially the script does the following:

  • runs and installs any updates
  • mounts a local backup HD
  • runs a program called rdiff-backup (for my personal data)
  • shutsdown to pc

This script is initiated by a Desktop/Panel icon. The advantage, for me, is that the machine is updated and backed up automatically every time I shutdown the pc - I am not involved, I can launch the script and then walk away whilst the updates and backups are taking place.

I think I understand the immutability of Silverblue but I was intrigued that when I installed it there were many ‘system’ updates that were downloaded/installed after I manually updated. Is this an initial install ‘thing’ and after that all updates are performed automatically (the system is immutable) or do you have to give permission to install updates?

I appreciate Ubuntu code and package management is completely different to Fedora but for those familiar the initial lines of my script is:

#!bin/bash
sudo apt --yes update
sudo apt --yes upgrade
sudo apt --yes autoclean
sudo apt --yes autoremove

I would like have a similar script (in terms of functionality) on my Silverblue install but I’m not sure how the immutability/manual permission to install works in practice. There is also the issue of updating flatpak apps where the is no user involvement. Apologies if this is very basic but I’m obviously a newbie and in a new environment. Thank you.

  • I did initially try using systemd to run this script on shutdown but it got too much for me to copy with. So I have an icon in my top panel that I use to run the script.
2

Hello @quarkradical and welcome to :fedora: !

Regarding updates, I would recommend reading the following if you haven’t already:

I’m not familiar with the tool you’re currently using to back up personal data. You could try it in the virtual machine you’re currently testing.

5

Thank you. I will have a good read and do some testing in my vm.

6

Fedora Atomic desktops are set up for the upgrades to take place in the background. On Silverbue, GNOME Software is in charge of automatic updates. That means:

  • Flatpaks are updates live, no need to reboot
  • The OSTree image gets updated in the background, i.e. a new deployment is being built usually on a daily basis. The current (booted) deployment is not being altered, hence there is no process of applying an upgrade on the existing system, as it happens with traditional systems (e.g. when shutting down, starting up, or applied on the live system). If you make a habit of restarting your system recurrently (say once a week), upon restart you’ll be on the latest tree image.
7

I don’t see any issue that would prevent you from doing that on Atomic Desktops. The commands would be different from what you are using right now but the behavior should be the same.

8

Mike B Thank you - very interesting. Is this functionality dependant on the Gnome flavour of Fedora Silverblue? E.g. would the same updating work on Fedora Budgie Atomic (which I think is the same as Fedora 43 Budgie)?

9

From the official docs I linked to in my previous post, i.e.:

OS updates are fully integrated into the desktop; you will be automatically notified when an update is available. On Silverblue and Kinoite, updates are automatically downloaded. This behavior can be changed in the settings. On Sway Atomic, Budgie Atomic and COSMIC Atomic, updates need to be manually applied.

Once an update is ready, it is just a matter of rebooting to start using the new version. There is no waiting for the update to be installed during this reboot.

1 Like