Available Bluefin base images

[manfredlotz]

I don't know how to find more or less some comprehensive information which Bluefin basic images are available.

Some of them seem to be

• ghcr.io/ublue-os/bluefin-dx-nvidia-open:stable
• ghcr.io/ublue-os/bluefin-dx
• ghcr.io/ublue-os/silverblue-main
• ghcrio//projectbluefin/bluefin-lts

Is there a list available with some info for each image?

[hamedrabah]

The maintained starting point is the Images catalog. It groups the images into Bluefin, Bluefin LTS, Dakota and Utah, explains their intended use, and links to package pages for published tags.

A couple of distinctions help with your examples:

• silverblue-main is a Universal Blue building base, rather than the complete Bluefin desktop. The Bluefin Containerfile uses it as its source image.
• The Bluefin LTS README's Images section currently documents ghcr.io/projectbluefin/bluefin-lts:stable and ghcr.io/projectbluefin/bluefin-lts-nvidia:stable, with CentOS Stream 10 as their base. That also gives you the correctly formed registry reference for your last example.

There is a documentation wrinkle: when I checked today, the rendered catalog's LTS card used ghcr.io/projectbluefin/bluefin:lts, while the LTS README used the names above; the Bluefin section also lacked image cards. The site says a major documentation update is in progress. So the catalog is useful for orientation, but I would cross-check a specific image against its repository README and package page rather than treating it as a complete, consistent inventory yet.

The catalog also explicitly says rebasing between Bluefin and Bluefin LTS families is unsupported, so they are not interchangeable release tags.

AI-assisted with GPT-6 via Codex; checked against the linked sources and the rendered catalog on September 6.

[castrojo]

You caught me on documentation day! Everything should be projectbluefin/blah by the end of the weekend.

[manfredlotz]

@hamedrabah First, thanks a lot for this.

If I understand correctly one should switch from "ublue-os" to "projectbluefin". Which means in my situation
ghcr.io/ublue-os/bluefin-dx-nvidia-open:stable -> ghcr.io/projectbluefin/bluefin-nvidia:stable

When I do this I get a build error

[4/4] STEP 12/15: RUN rm -rf /opt && ln -s /var/opt /opt
[4/4] STEP 13/15: CMD ["/sbin/init"]
[4/4] STEP 14/15: RUN bootc container lint --fatal-warnings
Lint warning: nonempty-boot: Found non-empty /boot:
  efi

Checks passed: 12
Checks skipped: 1
Warnings: 1
error: Linting: Checks failed: 1
Error: building at STEP "RUN bootc container lint --fatal-warnings": while running runtime: exit status 1
Error: Error: buildah exited with code 1

I fixed it by adding RUN rm -rf /boot/* in the containerfile after in the CLEANUP section just before the

### /opt

line.

Not sure if things could be done better.

[castrojo]

File all these as issues in projectbluefin/bluefin and we'll take a look, you're probably the first to try this so we need to fix the images asap. Thanks!

[manfredlotz]

Thanks to you. Done.

projectbluefin/bluefin#1208

[asormanni]

Hello,
is it possible that the projectbluefin/bluefin:stable image is behind ublue-os/bluefin:stable? I tried installing a test VM starting from the downloadable ISO, and this is what I see:

After fresh install & ujust update:

❯ uname -r
7.1.6-201.fc44.x86_64

~ 
❯ sudo bootc status
● Booted image: ghcr.io/ublue-os/bluefin:stable
        Digest: sha256:64001b955e90be9254e23e2a81f2dab88652f2158df73f45eee85cf248c01b99 (amd64)
       Version: 44.20260901 (2026-09-01T01:45:07Z)

  Rollback image: ghcr.io/ublue-os/bluefin:stable
          Digest: sha256:7dad244ef875a869115ea2760b0bc7fd3c6ffcc268d3d9b99d655171cae167b8 (amd64)
         Version: 44.20260714 (2026-07-14T01:55:19Z)

rebase to projectbluefin org:

> sudo bootc switch ghcr.io/projectbluefin/bluefin:stable --enforce-container-sigpolicy
> reboot


$ uname -r
7.1.3-201.fc44.x86_64

$ sudo bootc status
● Booted image: ghcr.io/projectbluefin/bluefin:stable
        Digest: sha256:383f523982a84cd23b40a8d252b50d6c4a65b013b03bfb70e74e0708fd8e082f (amd64)
       Version: testing-44.20260720 (2026-07-20T02:23:47Z)

  Rollback image: ghcr.io/ublue-os/bluefin:stable
          Digest: sha256:64001b955e90be9254e23e2a81f2dab88652f2158df73f45eee85cf248c01b99 (amd64)
         Version: 44.20260901 (2026-09-01T01:45:07Z)

In projectbluefin the version date is stuck to 20260720 (also on github release page), there also some packages are older (eg: kernel) comparing to those from ublue-os.

Am I doing something wrong, or is there simply a work in progress that hasn't been completed yet?

Regards.

[manfredlotz]

Yes, it seems to be behind. Also worth noting, the version is called testing-44

[manfredlotz]

Was updated recently and thus it is up to date now.