I don’t understand the answer though.
The answer is if you’re depending on software that is closed and out of your control (aka. you have an Nvidia card) then you should have support expectations around that hardware and linux.
There are no GTS ISOs because we don’t have a reliable way to make ISOs (the ones we have now are workarounds) but that should be finished soon.
If you depend on third party modules you’ll end up with third party maintenance - we didn’t purposely decide to break this we don’t work at Nvidia.
Do an update, this was an error due to moving over to dnf5.
Heya! I’m one of the ublue maintainers. I run the Project Pavilion at KubeCon, any chance you’re going? I love to talk about this stuff in real life! Our project is based on bootc, which is going into sandbox into the CNCF, so there’s lots of stuff to talk about!
Bluefin has even less. I consider this near-zero documentation.
What do you feel is missing from the documentation, can you be specific? You’re examples are too generalized to be actionable.
I would say it is the methodology. To distill it a bit more in the context of bazzite and universal blue:
FROM bazzite you can start from there.Dude, thank you for this. IMO reducing that down to simply “cloud native” is doing a disservice to how absolutely cool that methodology is.
The methodology IS cloud native, we didn’t invent this. 😼 People will update their terminology, we’re not doing anything new, Linux in infrastructure went through this a decade ago. It’s an update in vocabulary because it’s a shift away from the traditional distro model and has more in common with the rest of industry (k8s, docker, etc) than a desktop. The desktop is just the payload.
We know some people will complain but whatever, it’s our job to help people understand the tech and there are proper definitions for this stuff - The whole “immutables” or whatever slang people are making up doesn’t really make sense but we can’t control what people think, we can just do our thing and keep pushing out updates.
RancherOS doesn’t exist anymore, but a difference here is everything on the machine runs on the metal except whatever workload you have. Here’s people who do a way better job explaining it:
Our systems share the same tooling as Fedora CoreOS so this is probably a better example. You can make custom server images – we build on top of that too, similar to Bazzite but for server nerds: https://github.com/ublue-os/ucore - basically if you can script it, you can make an OS image out of it. Here’s bootc upstream where people are hanging out: https://github.com/containers/bootc/discussions
Hope this helps!
Yes, it’s a container like an app container you would deploy on docker or kubernetes.
It starts with a dockerfile with a FROM fedora, the difference is there’s an entire OS in there, with a kernel and everything. Then an action runs podman build on that container every day, which is then shoved into an OCI registry (in this case ghcr.io).
Then instead of each client doing package updates via a package manager it effectively does the equivalent of a podman pull on your laptop, and then stages the update for deployment on the device. Everything is running on the bare metal on the device, the cloud native part is the build process, pipeline, and delivery. Then rinse and repeat for updates.
It’s a bit like rancherOS except using podman.
Hi I’m the guy who posted the report. Your quote is exactly what it is, we use cloud native server tech to make Bazzite. Things like bootc, podman, OCI containers, etc.
all I want to run is a “normal” PC with a Linux distro.
That’s exactly what’s happening!
I don’t want is to have it running, or heavily integrated in some proprietary-ish cloud.
It does, just not ours, Valve runs that part. 😼 I’m happy to answer specific questions if you have any!
The noto fonts are in the main images, which bazzite is built from: https://github.com/ublue-os/main/blob/main/packages.json
Feel free to file issues there!
The entire purpose is to conveniently access your files, so if that’s a problem use containers normally or pass a -h during distrobox create if you want to isolate home directories.
bluefin/aurora co-maintainer here, the 1password ssh agent is a miniboss we haven’t conquered yet, just a heads up.
Hi! Universal Blue co-maintainer here, here’s the TLDR. You’ve got the basic descriptions right, “Universal Blue” is mostly the parent organization that holds everything in github.
We take Fedora’s Atomic OCI images and customize them for different use cases (Aurora, Bazzite, and Bluefin) and then publish base images so people can make their own versions of whatever they want. So if you wanted to take Silverblue, Kinoite, and make your own custom image you can mostly just grab whatever you want and shove it into an OS image. Bluefin started off as a “fix me” script for Silverblue that added all the stuff I wanted and then once I was shown what Fedora wanted to do with it the natural progression was to just make it a custom image. We just released 3.0 a few minutes ago actually!
Basically in Fedora 41 the tech will become more widely available with official OCI base images and better tooling. We just decided to start way earlier in the process so we could get all the automation out of the way, build a community, get familiar with it, etc. Happy to answer any other questions you may have!
ublue co-maintainer here. I go over a bunch of the reasons here: https://www.ypsidanger.com/homebrew-is-great-on-linux/
Namely we needed a way to complement Flatpak and brew was a natural fit. It’s an ecosystem reason not a technical one. It has everything we need and a good deal of Bluefin’s target audience are already using it on mac. So for us it’s an easier lift to just add homebrew and move on to larger problems.
Plus it’s nice that they’re working with the openssf to secure the supply chain pipeline, and it’s nice that everything is in github where we can inspect it, use the same tooling we use for the OS, etc.
Both podman and docker are on the image, you could just use containers normally without using devcontainers if you want.