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.

Thanks for the kind words! <3

there are a lot of tools included that are new to me, despite being a cloud-oriented developer.

Interesting! What tools do you commonly use?

We probably won't (we're not looking to grow that much anymore), but I think someone should definitely take either portainer or the proxmox stack and just slap it on top a CoreOS image with a user friendly installer and make a killer SMB server.

Here's the repo: https://github.com/ublue-os/bluefin and the intro doc outlines some of the features. We include all the codecs from rpmfusion and use negativo17 for the nvidia drivers.

Yeah it's 2024, this stuff should just be built into the OS! I'm at kubecon so don't have time to look into it now but it'd be an awesome thing to have, we'd love the help!

I'm not a security expert but I do know that the Homebrew is working with openssf on security: https://openssf.org/blog/2023/11/06/alpha-omega-grant-to-help-homebrew-reach-slsa-build-level-2/

Boxkit predates wolfi so it's still alpine, I'll probably replace it at some point but most of the forks of boxkit are because people want the premade github actions and they end up replacing it with whatever distro they want anyway. The wolfi connection is because I know the people who work there (including a ublue maintainer) and we have similar goals/ideas on how linux distros should be put together. My ideal dream is a wolfi userspace systemd-sysext on top of fedora base, then we can have our cake and eat it too!

We're not security experts but lots of us work in the field and that gives us access to peer review from experts when we set things up. We sign every artifact with sigstore so users can verify that the code used in github is what's on their image, that sort of thing. And most of our practices utilize CNCF governance templates that lots of other projects use.

Been there and done that. It's better to just not have the host OS break in the first place.

What package is it?

You use containers for your tooling, you purposely don't touch the host operating system, that's the entire point.

Yeah those don't go on your host they go in containers.

ublue contributor here. We're set up so you can install any cli program from any distro transparently. Should we outline that more in our docs?