Installing and using Fedora Silverblue

Silverblue Fedora is the workstation version of Fedora. It comes in the images that are created by using the rpm-ostree project. This read-only desktop operating system. It aims to be stable and reliable. In addition provides completely new experience of using Linux. The system is considered a test in Fedora, is being constantly improved and despite the seeming simplicity might not suit everyone. This “cheat sheet” for users already familiar with Linux.

Fedora as Silverblue and a program for writing to flash Media Fedora Writer take the official Fedora website. To record on a USB flash drive Silverblue 30 you Fedora program Fedora Media Writer, or other well known program.

Installing and using Fedora Silverblue

1.Installing Fedora Silverblue

Just want to warn you that Silverblue 30 not “friendly” to dual boot. It may work or it may not happen. It must be borne in mind. Details on the website: Documentation Fedora.(need to create an extended partition boot/efi) I hope in the 31st version will correct, but for now, that is what we have.

In Silvrblue no Live mode, it uses the Anaconda installer and the installation is fully identical to the regular Fedora installation. The entry in Silverblue possible only in the partition /var. When you partition the drive with separate partition for/home, the installer will make a symbolic link in /var/home. In detail the setup I will not stop.

Fill in all fields, we are waiting until the set restart. It is worth noting the installation and the deployment differently and takes more time than normal installation of Linux.

2. Configuring Fedora Silverblue

Silverblue has its own set of commands. All the commands rpm-ostree can be viewed in the terminal:

rpm-ostree --help
ostree admin --help


And also in Google:


The updated system(you need to wait until the download):

rpm-ostree upgrade

The first update will be long, and no monthly respins of the installer in Silverblue no, to see the download progress in the system monitor. Can be updated via Gnome-software, but I’m old-fashioned more trust in the terminal.

After updating reboot:

systemctl reboot

Then run Gnome-software and install repositories Fedora, reboot, optionally you can connect the repository Google-chrome.

After updating go over to settings, terminal, Nautilus browser and configure all by itself. Here too I dwell, I will not.

Default Silverblue looks like this:

Looking system:

rpm-ostree status

This command shows the completed deployment of the installed packages (LayeredPackages, LocalPackages), fixed shots.

As you can see in this picture, we have added the repositories Fedora and you can now install packages. In this initial setting is finished.

3. Kickbacks, reverse, Pina

One of the amazing features of Fedora Silverblue is easy of rollback system. Looking system:

rpm-ostree status

Take a picture, or rather secure the deployment system:

sudo ostree admin pin 0

Add for example the program screenfetch

rpm-ostree install screenfetch

systemctl reboot

I created a new deployment and fixed pin moved down. Unpin the:

sudo ostree admin --pin unpin N

Here N is the ordinal number of deployments from 0 to 2 in the current download (I confess to not immediately came up with that idea). In our case, the command would look like this:

sudo ostree admin --pin unpin 1

As you can see the was detached. Next, consider the Reset command. It removes all the installed packages, returns the system to the default view (with all personal files and settings are reset applications will stay):

rpm-ostree reset


systemctl reboot

As you can see now three deployments. First default(point on the left indicates what the currently used), the second previous to the reset and the third is our fixed pin.

Attached snapshot(snapshots), the system supports three last deployment. No fixed images two deployments(update, add packages that is creating a new deployment checkout the will be deleted).

Next, consider a Rollback, it can rollback to the previous snapshot:

rpm-ostree rollback


systemctl reboot

As you can see first and second images have changed places, the third fixed pin remained in place. It should be noted OSTree does not set fully all the pictures to disk, and loads the Delta.

As you can see three snapshots of the system size we have slightly less than 6 GB.

If the picture is not loaded, or just need to boot in a specific pin, you can select it in the boot menu. By default, the boot menu is hidden, you can See it holding after power, reset the ESC key in the EFI system and accordingly the Shift key on BIOS-based systems.

The boot menu I have (others too) is duplicated in four and six lines respectively, if two or three pictures in the system. I use the top second or third line. I hope in the next version Silverblue is correct. Clearing the cache:

rpm-ostree cleanup

With different keys:

sudo ostree admin cleanup

4. Flatpak

Silverblue designed for use Flatpak, and now we can connect all of them, or their choice. Flatpage in contrast to the usual RPM packages don’t require a reboot when installing or updating. Set the repository Flathub:

flatpak remote-add --if-not-exists flathub

Optional: beta Flathub:

flatpak remote-add flathub-beta


flatpak remotes

Firefox is not yet in flathub, but there is a repository with Firefox Nightly and Dev Edittion (supported by Red Hat).

flatpak remote-add --from org.mozilla.FirefoxRepo

Night of the GNOME application, there are many applications under development, if you want to try something not on Flathub or alternatively.

flatpak remote-add --if-not-exists gnome-nightly

flatpak remote-add --if-not-exists gnome-apps-nightly --from

Update Gnome-software, restart the system.

You can also remove unused repositories Flathub:

flatpak remote-delete "repo name"

The first set flatpage pulling with all the necessary libraries, dependencies and take up much space. Subsequent Flatpack, all this “economy” are used together, occupy less space, faster swing and set.

In the forums people write about using Snap and Appimage packages. I have not tried it myself, but they can also be kept in mind.

5.Installing local packages

Silverblue supports three types of packages.

  • LayeredPackages packet from the connected repositories are updated with the system.
  • LocalPackages – party RPM packages that are not updated.
  • Flatpak.

The command rpm-ostree does not own the search package, so you have to use workarounds:

Toolbox – install normal Fedora container, search DNF (discussed below).


rpm-ostree install dnfdragora

Search RPM:

List of installed packages:

rpm-qa | sort -fu > rpm-list-installed.txt

Search RPM package:

rpm-qa | grep httpd

Search through the Internet: And sites: Rpmfusion. Copr. Packages I try to install the list (lists) to reduce the number of reboots.

Installing RPM Fusion:

sudo rpm-ostree install$(rpm -E %fedora).noarch.rpm$(rpm -E %fedora).noarch.rpm


sudo rpm-ostree install firewall-config


rpm-ostree install chromium chromium-libs-media-freeworld


rpm-ostree install ffmpeg

Google-chrome (to include the repository in Gnome-software):

rpm-ostree install google-chrome-stable


rpm-ostree install gstreamer1-libav gstreamer1-plugins-bad-freeworld gstreamer1-plugins-ugly gstreamer1-plugins-ugly-free chromium-libs-media-freeworld ffmpeg

Virtualization (you can install Virtualbox or Gnome-boxes, I use Virt-manager):

rpm-ostree install virt-install libvirt-daemon-config-network libvirt-daemon-kvm qemu-kvm virt-manager virt-viewer virt-top


systemctl reboot

Starting libvirtd:

sudo systemctl start libvirtd

sudo systemctl enable libvirtd


systemctl reboot


lsmod | grep kvm

Add user to group libvirtd:

sudo grep -E '^libvirt:' /usr/lib/group >> /etc/group

sudo usermod -aG libvirt $USER

The developers Silverblue need to use with Flatpak. You can install all the applications locally.

And can be combined to supply all available from Flatpak.

The more the local system packages and third-party repositories, the slower it updates. The built in update time with the local packs I think. And may not be updated (he recently did the Reset, updated and corrected the list again and put local packages). It is also necessary to bear in mind. Fast update check:

rpm-ostree upgrade --check

6. Switching Silverblue

The team Rebase allows you to switch on any version of Fedora, regardless of what version we have installed. Update the version of the Linux distribution has always been an ambiguous and contentious issue. For example, I prefer reinstalling, someone update. Fedora Silverblue allows you to smoothly switch to a different version of what I will do now.

Check the available repositories ostree:

ostree remote list

Check the available repositories for rebase:

ostree remote refs fedora

As you can see to download the version available from 27 th to 32-th (rawhide). Choose the 31st version of the right bitness – 86_64 and updated:

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

Will have to download about 1GB of updates.

Waiting for the download, installation and after reboot:

systemctl reboot

Take a look:

As you can see, the system was updated on the 31st, and the second the 30-I Fedora. It’s almost like a dualboot. Next, I try the 31st to upgrade to rawhide:

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

As you can see established and 32 version. The update works without problems, the download speed increases gradually. If there are errors, you can enter the cancel command is:

rpm-ostree cancel

And start again. The work will not suffer. At the end you can clean the cache.

7. Desktop environment

In Silverblue can be set to add to Gnome and other desktop environment (further on only DE) with local packages. I don’t like “mess with DE” and prefer one DE system or DE+WM (window Manager).

The Fedora community is developing a branch Kinoite to use Fedora Silverblue with other DE. Again we take our default Silverblue. You can freeze the picture:

sudo ostree admin pin 0

Download GPG key:

curl -O

Add remote branch OSTree:

sudo ostree remote add kinoite --gpg-import


ostree remote list

Watch the available images:

ostree remote refs kinoite

As you can see, we have images of:

  • Base;
  • Deepin;
  • Kinoite;
  • LXQT;
  • Pantheon;
  • Silverrblue;
  • XFCE.

First try to install KDE:

rpm-ostree rebase kinoite:fedora/30/x86_64/kinoite

Download the order of 750MB, after installing restart:

systemctl reboot

So we have installed KDE with a minimal set of applications.

Next, view the image base:

rpm-ostree rebase kinoite:fedora/30/x86_64/base

Here we see a minimal Fedora Server. Then I switch to the saved pin 0 with default Fedora Silverblue and install XFCE:

rpm-ostree rebase kinoite:fedora/30/x86_64/xfce

Here we see Fedora XFCE. Next, I installed Deepin:

rpm-ostree rebase kinoite:fedora/30/x86_64/deepin

Here we see Fedora, Deepin. Next, I installed LXQT:

rpm-ostree rebase kinoite:fedora/30/x86_64/lxqt

Here we see Fedora LXQT. Next, I tried twice to install kinoite:fedora/30/x86_64/pantheon (Pantheon with the environment). Unfortunately, Pantheon I could not start may need to install it along with Gnome. Last I installed kinoite:fedora/30/x86_64/silverblue:

rpm-ostree rebase kinoite:fedora/30/x86_64/silverblue

It’s the same Gnome, but from the repository Kinoite. As you can see some of the other DE is quite a put in Silverblue from the repository Kinoite. To evaluate their work should be done on real hardware and use. Also keep in mind that this is not an official (perhaps yet) spins of Fedora, and the project of a single developer. Read more here. I still use the normal Fedora Gnome Silverblue c.

8. Toolbox

Toolbar – Toolbox pre-installed in Fedora Silvrblue 30. The project allows you easy to use containers for ordinary users. This is accomplished by using containers podman. The toolbar allows you to quickly and easily create a container with the usual Fedora installation, with which you can play or to develop separately from your system. I’m not a developer and have not yet found a use for the Toolbox itself. But the mention of him still stands. Toolbox supports:

  • Your existing user name and permissions;
  • Access to your home directory;
  • Common command-line tools, including the DNF package Manager.

In other words, containers toolbar look, feel and behave like the standard command-line environment of Linux. To start you need two simple commands:

toolbox create

This command will download the Fedora image file(500MB) and create from it a container of the toolbar. Then run:

toolbox enter

Once inside the toolbar you can get access to common command line tools and install the new one with the DNF. The output of the Toolbox:


The full list of commands can be viewed in the terminal:

toolbox --help


So the setup is Fedora Silverblue over. Your experience of using the questions, write in comments. In the next part I will write about the advanced settings Silverblue.

Learn more about the settings you can find on the official website. As well as good reviews in YouTube removed the blogger DorianDotSlash:


(Visited 499 times, 1 visits today)