this is going to be my personal experience of making custom ublue image. hopefully you will learn something from it.

so first of all you have to decide which Desktop Environment you want to use. I have chosen KDE but you can choose whichever DE you want. to see available DE you can go here. now copy the url of the image you want to modify. for my case it will be ghcr.io/ublue-os/kinoite-main:39.

create a file and name it Dockerfile. and add the following line to the Dockerfile

FROM ghcr.io/ublue-os/kinoite-main:39
# Install your favoutie program using rpm-ostree
RUN rpm-ostree install zsh fish neovim vim emacs kitty alacritty distrobox -y
# finally cleanup and commit the changes
RUN rpm-ostree cleanup -m && \
ostree container commit

save the file and run the following command in the current directory to build the image. (make sure you have docker installed on your system)

sudo docker build -t custom_image:latest .

you can now upload it to ghcr.io or rebase on it using rpm-ostree rebase command.

I hope this was useful. :)

  • Guenther_Amanita@feddit.de
    2·
    1 year ago

    For whom is it useful to write his custom image? Maintenance? Added value?

    It’s not good to layer too many packages on top of the normal atomic Fedora.

    If you still need a special configuration, like for Nvidia (“silverblue-main-nvidia”), gaming setup (“bazzite”), non-supported DEs/ TWMs (e.g. “deepin-main”) or special hardware (e.g. the Asus ROG or MS Surface), you can just download it and have everything in one go and working as a whole.

    This is not only very convenient, but also more reliable, since your baked-in Nvidia driver for example/ config is the same as the one from thousands of other users, including the developers.
    It prevents the “But it works on my PC”-problem and helps troubleshoot issues way faster and more precise.

    Anecdotally, KDE has been a mess for me everytime after a few weeks for example.
    This is due to package drift.
    On my Kinoite install, it is actually usable and doesn’t have nearly as many bugs as on the normal Fedora KDE variant. Just, because the install is the same.

    When is it useful to deviate from fedora and use a ublue version? You don’t have a fedora signed distro anymore. You have to trust another party blindly not to inject malicious code. Risk of not being maintained anymore.

    Pretty much always imo.
    Fedora isn’t allowed to ship some stuff ootb, and uBlue tweaks it for you.
    Also, you get more choice, as mentioned above.
    uBlue isn’t much derivated from the OG Fedora Atomic, and it has a large user base.

    It doesn’t need much maintenance, since it is mostly automated. That’s the main pro point compared to forked distros like Nobara. Also, it’s signed.