Fedora as a Server? Would You Do It? | Fedora Podcast 063

Plenty of sysadmins will tell you Fedora is a great desktop, a great place to build, and the wrong choice for a server. I have said some version of that myself. The question I wanted to put to us this week is whether that is still true, or whether it is a reputation from a few years ago that Fedora has quietly outgrown.

No guest this week. Just Noah and me, which means nobody was around to stop us going off topic.

A few things worth carrying away:

• The hesitation is almost never technical. This is the part that surprised me least and convinced me most. Noah’s answer to “what would it take for you to say yes” was not a release cadence or a support window. It was a path of escalation. His point is that most clients do not expect you to have every answer, they expect you to be able to say “I’m working on it, and here is who I’ve escalated to.” Fedora’s answer to that is a Matrix room, and for a bank or a hospital that is not an answer.
• “IT malpractice is a thing.” Noah’s line, and it landed. The distinction he draws is between what is responsible to run inside a given environment and what is not, and that line moves depending on who gets hurt when it breaks. My twelve containers of Plex and Audiobookshelf sit on one side of it. Medical imaging sits on the other.
• Three months of runway means different things to different people. For my home lab, three months to move off a Fedora release is luxurious. I was thinking a week. For an organization running thousands of servers under FIPS or HIPAA or PCI DSS, three months is roughly how long it takes to notice a new version exists. I still know shops running CentOS Linux 7, which retired five years ago.
• bootc genuinely does change the math, just not all of it. If the OS is an image you build and roll back rather than a thing you upgrade in place, the upgrade risk argument gets a lot weaker. What it does not fix is the escalation problem, because there is still nobody to call.
• Fedora is already shipping inside products you have used. Noah has first-hand experience with Fedora running inside commercial appliances, including one at a medical organization. The interesting wrinkle is that the appliance world has split: the point of sale system that has been humming along since the late 2000s and touches nothing, versus the modern always-connected appliance where every CVE is an emergency five minutes ago. Same Fedora, completely different risk posture.
• We went properly off the rails for a few minutes. Noah spent a while explaining why ad targeting feels like your phone is listening to you, and why it isn’t. The short version is that the algorithms are just very good at prediction, and everything they know about you is a boolean they vote on. I said out loud that we had very much slidden off topic. We left all of it in, because it was the best tangent we have had in a while.

Where we landed, after forty minutes, is “it depends,” which I have given as a professional answer more times than I would like. But the useful version of it is this: Fedora Server could technically run the world. Whether it should run your thing depends almost entirely on who you call when it breaks.

So we want your answer, and we mean it. Would you run Fedora on a server, and why or why not? Bonus points if you have actually done it in production and can tell us how it went. Comments, the Matrix room, or, as Noah correctly insists, RFC 1149.

Links from the episode #

• Fedora Server
• Fedora Server documentation
• Fedora bootc documentation
• FP054 BootC in the Wild
• FP062 What is Hummingbird
• RFC 1149, IP over Avian Carriers