How to rebase to Fedora Silverblue 36 Beta

Originally published at: How to rebase to Fedora Silverblue 36 Beta – Fedora Community Blog

Silverblue is an operating system for your desktop built on Fedora Linux. It’s excellent for daily use, development, and container-based workflows. It offers numerous advantages such as being able to roll back in case of any problems. Let’s see the steps to upgrade to the newly released Fedora 36 Beta, and how to revert if anything unforeseen happens.

Before attempting an upgrade to the Fedora 36 Beta, apply any pending upgrades.

Updating using terminal

Because the Fedora 36 Beta is not available in GNOME Software, the whole upgrade must be done through a terminal.

First, check if the 36 branch is available, which should be true now:

$ ostree remote refs fedora

You should see the following line in the output:


If you want to pin the current deployment (this deployment will stay as option in GRUB until you remove it), you can do it by running:

# 0 is entry position in rpm-ostree status
$ sudo ostree admin pin 0

To remove the pinned deployment use following command:

$ sudo ostree admin pin --unpin 2

Next, rebase your system to the Fedora 36 branch.

$ rpm-ostree rebase fedora:fedora/36/x86_64/silverblue

Finally, the last thing to do is restart your computer and boot to Fedora Silverblue 36 Beta.

How to revert

If anything bad happens — for instance, if you can’t boot to Fedora Silverblue 36 Beta at all — it’s easy to go back. Pick the previous entry in the GRUB boot menu (you need to press ESC during boot sequence to see the GRUB menu in newer versions of Fedora Silverblue), and your system will start in its previous state. To make this change permanent, use the following command:

$ rpm-ostree rollback

That’s it. Now you know how to rebase to Fedora Silverblue 36 Beta and back. So why not do it today?


Yesterday But some SeLinux issues were reported. It works OK at a glance anyway

בתאריך יום ה׳, 31 במרץ 2022, 13:05, מאת Michal Konečný via Fedora Discussion ‏<>:

I am getting an error during the post scripts. Any idea how to get this fixed?

Running post scripts... done
error: Running %post for akmod-nvidia: bwrap(/bin/sh): Child process killed by signal 1; run `journalctl -t 'rpm-ostree('` for more information

I’m not sure if nvidia is supported in Beta release. I don’t have a machine to confirm this. You can try to uninstall the akmod-nvidia, do a rebase and then try to install it back and see if this works.