j0rge

bluefin co-maintainer here. espanso is a hard one, we have an open issue on getting it to work because it'd be something awesome to include. We might end up needing to package it but haven't had a chance to look deeper into the issue.

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.

My Ubuntu installs are extremely reliable, both on desktops and servers.

Probably because you're an experienced user, not everyone has the same skillset.

mozillavpn

I would just overlay this, that's what it's there for, there's no need to do a full new image for VPN stuff.

We use quadlets to manage those containers: https://docs.podman.io/en/latest/markdown/podman-systemd.unit.5.html

As others in the thread have pointed out just having systemd manage them is the way to go, it's a nice combo!

What package is it?

If you kept a basic minimal Ubuntu host it would be trivial to maintain.

That's not true for most people.

I just don’t see the point. You want new users to understand containers.

You don't need to understand containers unless you're using the system for development -- which in Linux land means containers.

Most people aren't system administrators and they end up with broken computers for the most basic tasks. It's one of the major reasons why people hate using Linux desktops.

And even if you're an experienced sysadmin you can't account for the entropy that accumulates on traditional OSes. 18.04 -> 20.04 -> 22.04 doesn't end up being the same as a 22.04 clean install. This is a huge problem, especially for people who don't know how to manage linux systems. And the people who do manage systems at scale don't want that behavior either.

I go over this in this video: https://www.youtube.com/watch?v=hn5xNLH-5eA

But day to day I'm in an ubuntu container and using "normal" package management, I just don't do it on the host.

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.

Flatcar linux (this is what I use for my NAS/homeserver) and CoreOS are both good.

edit: OpenSUSE has microOS: https://microos.opensuse.org/