Upgrade Your Fedora Silverblue to Fedora 44: A Complete Migration Guide

Introduction

Fedora Silverblue is a desktop operating system built on the atomic update model of Fedora Linux. It’s designed for daily use, development, and container-based workflows, offering the unique advantage of being able to roll back to a previous state if something goes wrong. This guide will walk you through the process of rebasing your Silverblue installation to Fedora Linux 44—either using the graphical GNOME Software or the terminal. You’ll also learn how to revert the change if needed. By following these steps, you’ll enjoy the latest features and updates without losing the stability and flexibility Silverblue provides.

What You Need

• A Fedora Silverblue system already installed and running.
• Internet access to download the new image.
• Terminal or GNOME Software – choose your preferred method.
• Administrative privileges (sudo) for terminal commands.
• Time – the download and upgrade may take several minutes.

Step 1: Apply Any Pending Updates

Before rebasing, ensure your current system is fully up to date. This minimizes compatibility issues and ensures a smooth transition.

Terminal Method

Open a terminal and run:

$ rpm-ostree update

Graphical Method

Launch GNOME Software, go to the Updates tab, and install any available updates. After updating, reboot your system if prompted.

Step 2: Rebase to Fedora 44

You can perform the rebase using either GNOME Software or the terminal. Choose the option that suits you best.

Option A: Using GNOME Software (Recommended for Beginners)

1. Open GNOME Software and navigate to the Updates screen. You’ll see a notification that Fedora Linux 44 is available.
2. Click the Download button. This downloads the new image in the background – it may take a while depending on your internet speed.
3. Once the download completes, the Restart & Upgrade button appears. Click it. The system will prepare the upgrade and then reboot automatically.
4. After the restart, you’ll be running Fedora Linux 44. That’s it!

Option B: Using the Terminal (For Advanced Users)

1. Check availability of Fedora 44 refs. Run the following command to list remote references:

   $ ostree remote refs fedora

   Look for a line like fedora:fedora/44/x86_64/silverblue. If present, the image is ready.
2. (Optional) Pin your current deployment. If you want to keep the current system as a fallback in the GRUB menu (so it doesn’t get deleted during cleanup), pin it:

   $ sudo ostree admin pin 0

   Replace 0 with the index of the deployment you want to keep (check with rpm-ostree status). To remove a pinned deployment later, use:

   $ sudo ostree admin pin --unpin 2

3. Rebase to Fedora 44. Execute:

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

   This command downloads the new image and stages it for the next boot.
4. Reboot into Fedora 44. Finally, restart your computer with:

   $ systemctl reboot

   On boot, GRUB will automatically select the new deployment. After login, verify with cat /etc/fedora-release.

Step 3: How to Roll Back (If Something Goes Wrong)

Fedora Silverblue’s atomic design makes rollback straightforward. If you encounter boot issues or other problems with Fedora 44, follow these steps:

1. Boot into the previous version. During system startup, press ESC (or Shift on some systems) to show the GRUB menu. Select the entry with the older version (e.g., Fedora 43 or the previous deployment). Your system will start with that deployment.
2. Make the rollback permanent. Once inside the older system, open a terminal and run:

   $ sudo rpm-ostree rollback

   This command sets the older deployment as the default for future boots, reverting the rebase.
3. Clean up if needed. You can then remove the Fedora 44 deployment using rpm-ostree cleanup -p or simply leave it as a fallback (if unpinned, it may be removed later automatically).

Tips for a Smooth Experience

• Always update before rebasing – this reduces the chance of dependency mismatches.
• Pin your current deployment (especially if using the terminal) to ensure you have a guaranteed fallback.
• Check the Fedora release notes for any known issues or changes that might affect your workflow.
• Use a wired internet connection for large downloads to avoid interruptions.
• After upgrading, verify your installation with rpm-ostree status and confirm the deployment reflects Fedora 44.
• Keep at least one older deployment – you can manually keep it by pinning or simply not running cleanup until you’re confident in the new release.
• If using GNOME Software, be patient – the download may appear stalled but it’s working in the background. Check the activity log if unsure.
• For container-based workflows, note that Toolbox images may need to be recreated after the rebase to match the new host.

With these steps, you can confidently upgrade to Fedora Linux 44 on Silverblue and enjoy all the new features, while knowing you can always revert if necessary. Happy rebasing!