distribution-spec VS bazzite

Back in 2013, a little company called Docker made it really easy to start using containers to package up applications. A big key to their success was the OCI (you can learn about that here), an industry wide initiative to have standards around how we package up our applications. Because of OCI standards, we have hundreds (maybe thousands?) of tools that can be combined to manage and deploy applications. So why aren’t we using this for packaging up Notebooks and AI models as well? It would make deploying, sharing, and managing our models easier for everyone involved.

Kubernetes on the backend used to utilize docker for much of its container runtime solutions. One of the modular features of Kubernetes is the ability to utilize a Container Runtime Interface or CRI. The problem was that Docker didn't really meet the spec properly and they had to maintain a shim to translate properly. Instead users could utilize the popular containerd or cri-o runtimes. These follow the Open Container Initiative or OCI's guidelines on container formats.

OCI stands for Open Container Initiative, and its goal as an organization is to define a specification for container formats and runtime.

https://opencontainers.org/

Here is Containerfile from the repo: https://github.com/ublue-os/bazzite/blob/main/Containerfile

apko allows us to build OCI container images from .apk packages.

Flagger's load testing service can be installed via a Kustomization resource based on manifests packaged as an artifact in an Open Container Initiative (OCI) registry

CRI-O is a lightweight container runtime for Kubernetes. It is an implementation of Kubernetes CRI to use Open Container Initiative (OCI) compatible runtimes for running pods. It supports runc and Kata Containers as the container runtimes, but any OCI-compatible runtime can be integrated.

So somebody else created runj (runj is an experimental, proof-of-concept OCI-compatible runtime for FreeBSD jails.) https://github.com/samuelkarp/runj

Oh neat! Thanks for the information.

> running Steam on Bazzite (https://bazzite.gg) inside Proxmox.

Does this mean you can pass the gyro controls onto Steam Link or GeForce Now or some such? I have no interest in retro games, but it would be awesome to use gyro aiming for shooters...

https://github.com/ublue-os/bazzite/blob/main/Containerfile#... has, in addition to fan and power controls, automatic updates on desktop, supergfxctl, system76-scheduler, and an fsync kernel:

  rpm-ostree install rocm-hip \

I went looking for KDE, but was disappointed. From the FAQ on https://projectbluefin.io/:

> What if I want something like KDE or another window manager?

> Bluefin is an opinionated GNOME experience. However Universal Blue provides a maintained set of base images for anyone to be able to make a custom image. We hope Bluefin acts as an inspiration for others to build their own communities around user experiences. For example check out Bazzite if you want a great KDE gaming experience, similar to SteamOS.

The Bazzite link 404s, but there is info at https://universal-blue.org/blog/2023/11/08/bazzite-20/ and https://github.com/ublue-os/bazzite. Seems mostly focused on SteamDeck.

It's a cool list of patches.

I love these projects that bundle a bunch of cool things together with a base thing. Bazzite is a SteamOS project that similarly bundles all kinds of crazy things, and was a very popular recent submission, for another example. https://news.ycombinator.com/item?id=38828040 https://github.com/ublue-os/bazzite

The maintenance style here looks difficult. They seem to somehow take chunks of new chromium releases and make commits with those dropped in changes, and fix random stuff for a while. Looks very arduous. It makes me appreciate a somewhat opposed style, the Debian's Quilt model, where you have take the upstream and keep reapplying a set of patches to upstream. Maintaining is then just re-hacking any patches that break, and authoring new patches, whenever reapplying breaks. Seems like it'd be much easier to maintain, long run.

I was also hoping for something like the Quilt model because it seemed like it would be a good way to learn some shit about Chromium! Having the patches on hand would point to some key parts of the code-base, I feel! Im not sure how I'd learn what went into this fork, other than meticulously going through history. The readme also doesn't link to where it sources it's many patches from (which is another thing Bazzite did an excellent job of!).

Kind of interesting seeing a spreading focus on using more/modern x86-64 extensions spreading. Ubuntu is dabbling with what they are calling x86-64-v3, Red Hat too. https://www.phoronix.com/news/RedHat-RHEL10-x86-64-v3-Explor...

https://opencontainers.org/

Here is Containerfile from the repo: https://github.com/ublue-os/bazzite/blob/main/Containerfile

Hadn't heard of Bazzite.

> Bazzite is an OCI image that serves as an alternative operating system for the Steam Deck, and a ready-to-game SteamOS-like for desktop computers, living room home theater PCs, and numerous other handheld PCs.

https://github.com/ublue-os/bazzite/

Worth visiting the readme even if not interested. There's a huge list of included stuff, and a lot of it seems really cool.and helpful (for gamers or streamers mostly).

check out bazzite, it's basically steamos but fedora based instead of arch based, has the same immutable root layout for stability and smooth upgrades and as long as youre not using nvidia graphics you can use gaming mode with the bazzite-deck image