Basically Fedora Silverblue, except my own golden image version of it... get it?
With thanks to uBlue and Seraphim Strub for inspiring much of the work in this repo.
- Install Fedora Silverblue from bootable ISO.
- Log into Container Registry via Podman:
sudo podman login git.infected.systems:5050
- Copy the
auth.json
so thatrpm-ostree
will find it:
sudo cp -v /run/containers/0/auth.json /etc/ostree/auth.json
- Reset our overlays (if we're using localisation then we might have packages that get automatically layered like
langpacks-en_GB
, which can cause problems when rebasing):
sudo rpm-ostree reset
- Rebase to Goldenblue (without validating signatures, so we can import the sigs):
sudo rpm-ostree rebase ostree-unverified-image:docker://git.infected.systems:5050/infectedsystems/goldenblue:40
- Reboot
- Now we can switch to validating signatures on the Goldenblue image:
sudo rpm-ostree rebase ostree-image-signed:docker://git.infected.systems:5050/infectedsystems/goldenblue:40
- Reboot
To configure local Distrobox containers, run:
distrobox assemble create --replace --file /etc/distrobox/distrobox.ini
To enter a Distrobox container, enter one of the following:
distrobox enter fedora
distrobox enter ubuntu
distrobox enter wolfi
The BlackBox terminal emulator (installed via Flatpak by Yafti) is configured in dconf
to start up using distrobox enter fedora
as the initial command, so opening the BlackBox shortcut will drop you directly into an Fedora Distrobox. This is also mapped to the Ctrl
+ Alt
+ F
desktop shortcut using dconf
.
To debug whether any core issues you are facing are part of a custom image or also exist upstream, you can temporarily rebase on the upstream Silverblue image like so:
sudo rpm-ostree rebase ostree-image-signed:docker://quay.io/fedora/fedora-silverblue:40
- This image is not currently built for
aarch64
. I'm aiming to fix this in future. - I cannot offer any support for this image. You're on your own here if you try and use it.