Updates, Upgrades & Rollbacks
Installing updates with Fedora Kinoite is easy and fast. It also has a special rollback feature, in case anything goes wrong. Additionally, you can choose to have multiple versions of your operating system installed at all times, and you can choose which one to boot into whenever you start up your system.
OS updates in Fedora Kinoite are not yet integrated into Discover (see progress in issue 133).
Until support is fully implemented, you will have to update using the command line. To do this, run:
$ rpm-ostree upgrade
This will check for new updates and download and install them if they are available. Alternatively, to check for available updates without downloading them, run:
$ rpm-ostree upgrade --check
Upgrading between major versions (such as from Fedora 35 to Fedora 36) can not yet be completed using Discover. Until support is fully implemented, you will have to upgrade to a new major versions using the command line.
First, verify the branch is available. You can print all available branches with this command:
$ ostree remote refs fedora | grep kinoite
After you’ve verified the name of your branch, you are ready to proceed. For example, to upgrade to Fedora Kinoite 36, the command is:
$ rpm-ostree rebase fedora:fedora/36/x86_64/kinoite
Currently, the default remote for Fedora Kinoite 36 is named
The process is very similar to a system update: the new OS is downloaded and installed in the background, and you just boot into it when it is ready.
Additionally, you can choose to rebase to a different immutable variant of Fedora, like for example Fedora Silverblue. Fedora Siverblue is similar to Fedora Kinoite, except for the fact that it uses the GNOME desktop environment instead of the default Plasma desktop environment.
What this means is, you can rebase to Fedora Silverblue to try it out, without ever touching your current system. Because the two system images are isolated from eachother, the two desktop environments will never be installed at the same time. All of your flatpak apps and /home files will stay persistent between rebases. Same applies for testing out the bleeding-edge version of Fedora Kinoite, which is Rawhide.
If you decide to rebase, make sure to pin your current deployment, so you don’t accidentaly lose it (by default, only the two most recent deployments are kept).
Fedora Kinoite keeps a record of the previous OS version, which can be switched to instead of the latest version. While this shouldn’t usually be necessary, it can be helpful if there is a problem with an update or an upgrade (rollbacks work the same way for both), as well as for development purposes.
There are two ways to roll back to the previous version:
Temporary rollbacks: to temporarily roll back to a previous version, simply reboot and select the previous version from the boot menu (often known as the grub menu).
Permanent rollbacks: to permanently switch back to the previous deployment, use the
After rolling back, you will technically be on an old OS version, and may be prompted to update. Updating will undo the rollback, so should be avoided if you want the rollback to stay in effect.
Want to help? Learn how to contribute to Fedora Docs ›