Guide to Installing and Mastering Fedora Silverblue: An Immutable GNOME Desktop with rpm-ostree and Flatpak

Fedora tutorial - IT technology blog
Fedora tutorial - IT technology blog

Comparing Desktop Operating System Management Approaches

Think of an operating system like a rental apartment. In traditional Linux distributions such as Fedora Workstation or Ubuntu, whenever you install a library or tweak a configuration file, you are directly altering the building’s structure. One day, a hidden conflict in an update breaks your display server. You are greeted by a black screen, spending the entire morning troubleshooting and removing packages in TTY mode.

An immutable operating system (Immutable OS) tackles this problem with an entirely different mindset:

  • Traditional Operating Systems (Mutable OS – Fedora Workstation, Ubuntu): The entire system filesystem is writable. Package managers like dnf or apt overwrite binaries directly in /usr. If a power outage occurs while installing a new kernel, the system can easily end up in a broken, half-installed state.
  • RAM-based Operating Systems (Live OS / Stateless): Everything is loaded directly into volatile memory. Shutting down wipes all data clean. While extremely secure for public kiosks, it is impractical for a daily workstation.
  • Git-like Immutable Operating Systems (Fedora Silverblue): The system locks down /usr as strictly read-only. Directories like /var and /etc remain writable for configurations and user data (with /home actually symlinked to /var/home). Each update functions like an atomic commit. The OS downloads the entire new image intact and swaps the deployment only upon reboot.

Real-World Pros and Cons of Fedora Silverblue

After using Fedora as my primary development machine for over two years, I decided to give Silverblue a try. The experience has been both exciting and mind-shifting.

Key Advantages

  • 30-second rollbacks when issues arise: Did this morning’s update break your Wi-Fi driver or crash GNOME? Simply reboot, bring up the GRUB menu, and select yesterday’s deployment. Everything is instantly back to normal.
  • Clean separation between OS core and user applications: Browsers, Slack, Spotify, or VS Code all run independently via Flatpak. Applications cannot tamper with system files or interfere with core libraries.
  • Pristine development environments: Need Node.js 18 for a legacy project and Node.js 22 for a new one? Instead of cluttering your host system, spin up two separate Toolbox containers. Your base OS remains as clean as a fresh install.

Trade-offs to Keep in Mind

  • System package installation takes longer: The rpm-ostree install command takes 45 to 90 seconds to rebuild the binary tree image. Afterward, a reboot is required to fully apply changes.
  • Unlearning the sudo dnf habit: You can no longer casually run install commands directly on the host. You must categorize your tools: GUI apps go to Flatpak, dev tooling lives in Toolbox, and only drivers or kernel utilities are layered onto the base OS.

When Should You Choose Fedora Silverblue?

This distribution is tailor-made for those who prioritize rock-solid stability—powering up your PC to work without the constant dread of system breakage after an update. Silverblue is especially ideal for:

  • Developers looking to experiment with cutting-edge tech without cluttering their main system.
  • Users seeking a low-maintenance, macOS-like desktop experience on an open-source foundation.
  • System administrators wanting to deploy identical, consistent configurations across fleet workstations.

Conversely, stick with standard Fedora Workstation if you frequently compile custom kernels, install out-of-tree drivers, or heavily tweak low-level OS hooks. If you love the immutable paradigm but prefer an alternative desktop environment, consider exploring Fedora Sericea for Sway or Fedora Onyx for Budgie.

Installation and Mastery Guide

1. Operating System Installation

Download the Silverblue ISO from the official Fedora website and write it to a USB drive using Fedora Media Writer. The Anaconda installer will detect your hardware. When partitioning the drive, select Automatic Partitioning. Silverblue requires a standard Btrfs subvolume layout (comprising root, home, and var) for its snapshot mechanism to function properly.

2. Managing the System with rpm-ostree

Log into GNOME, open a terminal, and inspect the system status:

rpm-ostree status

The terminal will display the current commit hash, deployment branch (such as fedora:fedora/41/x86_64/silverblue), and any layered packages. This model aligns closely with the evolution toward bootc container operating systems in the Fedora ecosystem.

To upgrade the entire operating system, simply run:

rpm-ostree upgrade

The download and image staging happen completely in the background. You can continue browsing the web or listening to music without interruption. Once finished, just restart your machine whenever convenient.

3. Layering Essential System Packages

Layering is the technique of adding RPM packages directly onto the base ostree commit. Reserve this strictly for hardware drivers (like NVIDIA), preferred shells, or virtualization daemons:

# Install monitoring tool and fcitx5 Vietnamese input method into the OS layer
rpm-ostree install htop zsh fcitx5 fcitx5-unikey

If you want to test the package immediately without rebooting, use the experimental live-apply flag:

rpm-ostree apply-live

Removing a system package is just as straightforward:

rpm-ostree uninstall htop

4. Managing GUI Applications with Flatpak

All daily desktop GUI applications should be installed from Flathub to ensure sandbox security:

# Enable the official Flathub repository
flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

# Install browser and code editor
flatpak install flathub com.google.Chrome
flatpak install flathub com.visualstudio.code

Flatpak applications run in isolated sandboxes, minimizing the risk of malicious software snooping on sensitive local files.

5. Setting Up a Clean Dev Environment with Toolbox

Toolbox provides fully privileged Fedora containers that seamlessly share your /home directory and host network. Your source code lives on the host filesystem, while development runtimes execute entirely inside the container:

# Create a new dev workspace
toolbox create dev-workspace

# Enter the container
toolbox enter dev-workspace

From here, you are free to run familiar dnf commands to install compilers and libraries:

sudo dnf groupinstall "Development Tools"
sudo dnf install nodejs python3-devel

If dependencies become messy after months of experimenting, you can simply destroy and recreate the container in seconds. The host system remains completely untouched.

6. Emergency Recovery with Rollback

Ran into an issue after layering a new package? Just run a single command:

rpm-ostree rollback

Reboot your machine. The system switches back to the previous deployment, restoring everything to its working state. No more reinstalling your OS from scratch whenever something breaks.

Share: