3,486 karma · joined March 22, 2011
I'll bring it up during the next bootc meeting[1], which are public btw! Thanks for using bazzite!
1: https://github.com/bootc-dev/bootc?tab=readme-ov-file#commun...
The author mentions this as well but there's no details there. We've been shipping chromeos-style images with universal blue for over 4 years and the ostree parts are invisible to end users. What do you feel takes away from the user experience?
One of my fondest memories was making my own steamOS with Clear Linux: https://community.clearlinux.org/t/notes-on-building-a-clear...
And now I work on bazzite.gg, thanks for making a kickass OS Arjan and Co!
https://artifacthub.io/docs/topics/repositories/
You can do the same with just about any K8s related artifact. We always encourage projects to go through the process but sometimes they need help understanding that it exists in the first place.
Artifacthub is itself an incubating project in the CNCF, ideas around making this easier for everyone are always welcome, thanks!
(Disclaimer: CNCF Staff)
This is a fantastic idea, it sucks to have an upgrade blocked by a slow repo, if you wouldn't mind filing an issue or sending a PR I'd love to have this. Thanks for the feedback!
Contributor here, we've been working on this diligently over the past cycle (the rest of the org is mostly done, Bazzite is largest so we're only getting to it now). We're hoping to be done over the summer with published SBOMs and all that good stuff.
Here's the issue for homebrew on linux/arm: https://github.com/Homebrew/brew/issues/19208
And here's the FOSDEM talk: https://fosdem.org/2025/schedule/event/fosdem-2025-6373-home...
Hah this isn't just the court, everyone who plays this game has to watch YouTubers explain it because they don't do it in the actual game.
They've been there for 20 years already.
We have indeed been playing with this! We think it's a great compliment to extending an ostree OCI base image and hope to bolt on all sorts of goodies. Lots of cool innovation happening in this space right now, it's awesome stuff.
Do people think that distribution developers are hand combing through all those apps? Untrusted by default is more scalable.
Rest in peace friend. :(
Themes work like they do in normal Fedora.
You can always create containers with init if that's how you want to do that though. Some distros publish images that come that way: https://github.com/89luca89/distrobox/blob/main/docs/useful_...
I'm using Prompt, it's a new terminal designed to make the toolbox/distrobox flow much nicer: https://gitlab.gnome.org/chergert/prompt
It's still relatively new so it isn't on flathub yet but it makes everything mostly seamless.
Though distrobox is bash so maybe running the older version in your home directory would have been a good bandaid in the meantime, maybe I should write that up as a tip?
But yeah +1 on distrobox!
We found that people struggle with the pet toolbox pattern so we send them right to the devcontainer pattern. This is an area where we differ from Fedora. It should just come set up out of the box.
The reason it had to be Fedora was because I can't do this with Debian or Ubuntu. Fedora had the tech but I still enjoy the Ubuntu/Debian part of the OS. Since distrobox exists I can replicate a reasonable facsimile of the native distro with an ubuntu container and a more ubuntu-like desktop.
This project uses this upcoming feature in Fedora: https://fedoraproject.org/wiki/Changes/OstreeNativeContainer... and switches to its consumption model entirely.
On stock Fedora you're pulling from a distribution-hosted ostree endpoint to do updates. With Bluefin (and other universal-blue.org images) you're pulling from a container registry (in this case ghcr.io, but you can push your builds to any registry or host your own).
We ingest Fedora daily and then add codecs, a bunch of hardware enablement support via udev rules, add a few pain-in-the-ass-otherwise things like the obs virtual cam, xbox controller support, etc. Then that image is pushed to ghcr.io and the local package manager uses that.
We also enable Flathub out of the box and Distrobox: https://github.com/89luca89/distrobox - then ship a few preconfigured boxes for you to play with: Ubuntu, Fedora, and Wolfi.
Then we have another image that you can rebase to by typing `just devmode` in a terminal which adds vscode with devcontainers, devpod, devbox, kvm/qemu, incus/lxc/lxd, some nice monospace fonts, cockpit, kind, docker, and a bunch of associated cluster tools.
And since we build everything in CI there's no local package conflicts like in upstream Fedora when the main repo and rpmfusion repos are conflicting, your PC only ever gets successfully built images.
If you have an AMD Framework the gnome-power-profiles manager has the inprogress patches from AMD already included and are probably better. Upstream Fedora is also in the process of evaluating `tuned` so in the future there may not even need to be a separate image for Framework.
Rebase instructions here: https://universal-blue.org/images/
And then all the developer patterns are cloud native like devcontainers instead of using the host packages, included k8s, podman, and docker tooling, etc.
`rpm-ostree` grew OCI support, which lets us build the entire thing with a dockerfile and github actions, which is much easier, we can run the entire thing out of github.
It would be awesome if you could use Debian for this but alas, no one has made a `deb-ostree`. If someone did it wouldn't be too hard for Universal Blue to publish Debian-based images.