Russia Today comes to mind

Sure, but for Russia it’s the actual doctrine: https://en.wikipedia.org/wiki/Russian_military_deception

you’re a rock star

The top level management: CEO, CFO, CTO etc. Basically, the big bosses.

deleted by creator

I don’t know if this works in docker (usually there is 1:1 equivalency between the two), but with podman you can do something like:

podman stop --filter name=foo

man podman-stop tells us:

   --filter, -f=filter
       Filter what containers are going to be stopped.  Multiple filters can be given with multiple uses of the --filter flag.  Filters with the same  key  work
       inclusive with the only exception being label which is exclusive. Filters with different keys always work exclusive.

Maybe I don’t understand the question, but what prevents you from adapting your Ansible playbooks to Fedora Silverblue? I assume for Debian at some point you have a “install packages” section which you should rewrite to use rpm-ostree or flatpak instead of apt-get; your dotfiles section should remain the same etc etc.

In the FTPD logs, do you see the initrd file being pulled? Could it be a mismatch between the kernel and initrd you’re serving?

Well, I don’t know how fair they play now, but for sure that wasn’t always the case.

Let’s not forget Oracle! While Rocky bit the bullet with this poorly written announcement, I believe Red Hat’s target was in fact Oracle, not some 20 employees startup with no customers.

Well, Red Hat doesn’t really get paid (of course, I’m not arguing RH is not making or doesn’t have enough money) – they would get payed for one or a very small number of licenses. At the same time, Rocky (and Alma and more importantly Oracle) wants to actually sell (albeit only support) the same product put together by Red Hat so it’s not really a community RHEL clone. I think that’s the real issue here. I wouldn’t have a problem with this workaround if it were coming from the community, without the commercial asterisk attached.

I’ve been using the same Silverblue installation for about two years (maybe even more than that). Initially, I did a lot of tweaking because I didn’t really know how to approach toolbox and flatpaks, especially because I don’t use Gnome as my desktop environment, so this system went from standard Silverblue to Silverblue+i3 overlayed, then to Silverblue+sway overlayed, recently it got rebased to Sericea and it’s still running like day one. It also got upgraded from version 35(-ish) to 38 still without any issues (well, I did have some issues, but I simply rolled back and that fixed it).

I’m also deploying several Fedora CoreOS servers with a similar level of success, but those mainly tend to just run some containers, so I would say I mess way less with those, it’s been mostly just update/upgrade to the latest, check if podman is still running my containers and let them be.

For all my non-compliant, non-supported hosts I started using Fedora CoreOS quite successfully.

If you package your applications as containers, you should have a very easy time with it. It’s based off ostree, which means a couple of things:

• immutable (so not easy to break, I guess?)
• atomic upgrades, which means you upgrade in a single step
• atomic and full rollbacks, which means if an upgrade breaks your host, you can rollback to the exact previous version booted simply by choosing it from grub
• still based on rpm, so you will still have a grasp of it, even though many things are completely different
• other benefits I forgot, I’m sure :)

All with the added benefit that once you go towards containers you can change your distro with minimal effort, so there’s that.

I don’t think Arch (or any rolling distro for that matter) is the best solution for a server deployment. If you update rarely, you’re bound to have to do manual interventions to fix the update. If you update too often, you might hit some distro breaking bug and you’re rebooting very often as well. Those two options are not great on something requiring stability.