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. :)

  • beta_tester@lemmy.ml
    0·
    10 months ago

    Thx for the write up. I’d be itnerested in the following.

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

    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.

    • Björn Tantau@swg-empire.de
      0·
      10 months ago

      It’s useful when you need something custom. Bazzite, an alternative OS for the Steam Deck and other handheld PCs, is built that way.

      Or if you want one for your company.

    • d3Xt3r@lemmy.nz
      0·
      10 months ago

      It’s useful for those who are interested in using an immutable OS. An immutable OS has several advantages over regular OSes, such as reliable and atomic updates, easy rollbacks, increased stability etc. However, a major drawback with immutable OSes is customisation - because certain key parts of the system are read-only, you may be limited in what you can change. Fedora Silverblue/Kinoite solves this to some extent by using ostree, and rpm-ostree to install packages in a layered fashion. The problem with that though is that it can significantly increase update times and also bloats up your system, which is a concern if you’ve got a lot of packages installed in that manner. Plus, there’s also the issue of limited customisations - maybe you want to switch to a completely different DE for instance.

      This is where making your own custom image comes in handy. When you fork the template, you can put in all your customisations on git, and your custom image gets built automatically.

      You have to trust another party blindly not to inject malicious code

      But you’re doing that anyway with pretty much every piece of code/app/website that you use without auditing it yourself, so what makes this any different?

      In any case, at least with uBlue you don’t have to blindly trust anyone because everything in uBlue is fully open and transparent, you can see for yourself exactly what’s being done - in plain text.

      Risk of not being maintained anymore.

      Not really an issue. This isn’t a distro, it’s literally just a script which builds your own distro using upstream code, which is pulled from Fedora. So the only real risk is if Fedora decides to shut shop or something. But even if they did, someone else would fork it, and you could just rebase to that fork and move on.