Upgrading Fedora Silverblue to Version 44: A Complete Rebase Walkthrough

By ● min read

Overview

Fedora Silverblue is an immutable desktop operating system built on Fedora Linux. It leverages rpm-ostree for atomic updates, making it ideal for daily use, development, and containerized workflows. A rebase is the process of switching your Silverblue system from one major Fedora release to another—in this case, from an older version to Fedora Linux 44. Unlike traditional dist-upgrades, rebasing is safer because it keeps your current deployment intact, allowing a simple rollback if something goes wrong. This guide explains both the graphical and terminal methods for rebasing, plus how to reverse the operation if necessary.

Prerequisites

• A working Fedora Silverblue installation (version 43 or earlier).
• A stable internet connection (the new image is several hundred MB).
• Sufficient disk space (at least 5 GB free).
• Basic familiarity with the terminal (for the CLI method).
• Optional: backup important data, though Silverblue’s atomic nature makes major issues unlikely.

Step-by-Step Guide

1. Update Your Existing System

Before rebasing, apply all pending updates to ensure a clean starting point. Open a terminal and run:

rpm-ostree update

Or use GNOME Software to install updates. After updating, reboot your computer.

2. Rebasing Using GNOME Software (GUI Method)

GNOME Software will automatically detect when a new Fedora release is available. Navigate to the Updates screen. You should see a banner advertising Fedora Linux 44. Click Download to fetch the new image. This may take a few minutes depending on your internet speed.

Once the download completes, the button changes to Restart & Upgrade. Click it, and your system will prepare the new deployment and reboot into Fedora 44. That’s it—no further steps required. The old deployment remains available in GRUB for rollback.

3. Rebasing Using the Terminal (CLI Method)

For users who prefer the command line, the terminal method offers more control.

Verify the Target Branch

Check that the Fedora 44 branch is accessible from your configured remote:

ostree remote refs fedora

Look for an entry like fedora:fedora/44/x86_64/silverblue. If it appears, you’re good to proceed.

Optional: Pin the Current Deployment

Pinning prevents the current deployment from being garbage-collected after the rebase. To pin the first entry (index 0) from rpm-ostree status:

sudo ostree admin pin 0

To later remove a pin, use:

sudo ostree admin pin --unpin 2

Replace 2 with the actual deployment index.

Perform the Rebase

Now rebase to the Fedora 44 branch:

rpm-ostree rebase fedora:fedora/44/x86_64/silverblue

This command downloads the new image and sets it as the next boot target. When finished, reboot:

systemctl reboot

Your system will boot into Fedora Linux 44. If you encounter issues, proceed to the rollback section.

4. Rolling Back to the Previous Version

If Fedora 44 fails to boot or you experience problems, a rollback is straightforward.

Boot into the Old Deployment

At the GRUB menu, select the entry labeled with your previous Fedora version (e.g., Fedora 43 or 42). If GRUB doesn’t appear, press ESC during boot. Once you’re back in the old system, you can make the change permanent.

Permanent Rollback via Terminal

Run the following command to set the old deployment as the default:

rpm-ostree rollback

After that, reboot. Your system will now boot into the old release every time. The failed Fedora 44 deployment remains in the boot menu but won’t be used unless selected manually.

Common Mistakes & Troubleshooting

• Skipping the update step: Rebasing from an outdated system may cause dependency conflicts. Always run rpm-ostree update first.
• Not pinning important deployments: If you don’t pin, the old deployment may be automatically removed after a few weeks, making rollback impossible. Pin if you want to keep it long-term.
• GRUB menu not showing: Some systems have GRUB timeout set to 0. Press ESC repeatedly right after the BIOS screen to force the menu.
• Ignoring error messages during rebase: If the rebase command fails due to network issues or missing refs, check your internet connection and the remote configuration (ostree remote list).
• Forgetting to reboot after rebase: The new image is only deployed after a reboot. Without it, you’ll remain on the old system.

Summary

Rebasing Fedora Silverblue to version 44 is a safe, atomic process that preserves your previous deployment for easy recovery. Whether you use GNOME Software or the terminal, the steps are straightforward: update, rebase, reboot. If something goes wrong, GRUB and the rpm-ostree rollback command let you revert instantly. With this guide, you can confidently upgrade your Silverblue system to the latest Fedora release.