How to learn more about available images?

Hello, lately I’ve been thinking about trying out more ublue images, but I found that the image list is a bit hard to navigate and get info from, mainly because of these reasons:

  1. Big list of images with no categorisation
  2. Hard to understand if image is deprecated or not
  3. Name and description don’t provide enough info (e.g., onyx, lazurite, vauxite - interesting names, but what do they do?)

Sometimes the image has a github page which helps uncover some info, but not always.

This made me wonder if there is a different way I’m supposed to go about finding/learning about available images?

Thank you very much for your help and patience :slight_smile:

You’re not doing it wrong we just need a volunteer to improve the website. :smiley:

1 Like

Hello,

I also was quite confused/disappointed in looking at the github package list not knowing what the variations are. This forum seems like the best way to at least start the conversation as to what it all means. Here is what I found with links.

They mostly are from the fedora spins, the naming is half mixed between DE+Atomic or having some sort of rock term (i.e. kinoite).

Going off of this list first:

You may see some old repos if you go searching on the ublue-os github, but they will point you back to this first list.

This list is mostly similar to the fedora registry, and it’s associated gitlab.

These images also can have variations for Nvida.

One missing from main is Cosmic, but that is handled on its own.

There are others that are also fedora spins but have not been made atomic or do not have much support. Such as cinnamon or i3.

After this you get into a different class of images which are more “feature complete”. They are generally the most user friendly in terms of installed application and use.

  • Bluefin - GNOME
  • Aurora - KDE
  • Bazzite - KDE or GNOME

Bazzite goes into its own project with its own list of images. but within this scope falls into this category.

There is also a more experimental homelab type image with ucore. These images are generally more server based and meant to have zfs pools or network shares.

There are many other image variations such nokmods from the first list. This seems to be the difference between vanilla fedora kernel/modules and Ublue modifications.

There is also the Dx vairiants for bluefin/aurora which add more development focused features, easiest example being virt-manager. Bazzite is planning to implement a DX variant, but is still an open issue.

Everything else would fall as unoffical or custom created images. These are mostly community images with a noteworthy being wayblue which has a hyprland build.

Relevant Brodie Robertson Video

1 Like

That page redirects to Packages · Universal Blue · GitHub
I tried searching for lxqt and fount lxqt and lxqt-main, I decided to go with lxqt-main as the other one is an archived repository, ran the command docker pull ghcr.io/ublue-os/lxqt-main:sha256-c495e350b1af0a7f881a087294fb5fa39dd7f40fea060f3fc25667212bd0494b.sig as per instructions after installing docker with rpm-ostree, but the procedure failed. It seems the only two desktops available are Gnome and Plasma, which are both heavy for older hardware, is there any lightweight option for using this project?

The lxqt option is called lazurite, it replaced the lxqt package: lazurite-main versions · ublue-os · GitHub

Will rebasing to lazurite bring the same “battery included” benefits as Bluefin or Aurora? Like auto-updates to major Fedora releases etc.? Is it possible to download an iso for installing lazurite directly without installing Bluefin and then rebase?

I also see rebasing to Silverblue is possible, all versions including nvidia, surface etc. I don’t understand how these releases are maintained. Are they part of Universal Blue? Why maintain Silverblue when you already ship Bluefin?

Could you expand on the scope of this project and subprojects?

These are base images designed for people to make their own custom images (Bazzite and Bluefin are built off of these). They’re a common base for people to build off of, sometimes it makes sense to fix a thing in the base images than in a downstream image. Automatic updates are turned on for all of these by default.

We don’t make ISOs for these and are generally not recommended for every day usage, they’re more like soup stock than final products. Though anyone can grab a base image and build a “Bluefin but it’s lazurite”, wire up the ISO generator, etc. and publish builds if they want.

We don’t plan on expanding the scope of Universal Blue any further as the project is mostly complete and in sustainability mode.

1 Like