I use Fedora Kinoite daily and find it to be the only OS to make sense really.
I find Fedora CoreOS totally confusing (with that ignition file, no anaconda, no user password by default, like how would I set this up anywhere I dont have filesystem access to?)
But there are alternatives. I would like to build my own hardened Fedora server image that can be deployed anywhere (i.e. any PC to turn into a secure and easy out-of-the-box server).
As modern server often uses containers anyways, I think an atomic server only makes sense, as damn Debian is just a pain to use.
Experiences, recommendations?
@Pantherina i use fedora kinoite and yeah it’s really awesome! new packages and a safe system.
I wanted to use Fedora CoreOS on my server but no providers offer it so I ended up installing AlmaLinux instead. But yeah the ignition file setup is really painful. tried in a vm but never managed to get everything i wanted. i’m gonna stick with enterprise linux until they make it easier, i think
I tried IOT too and it the bootloader didnt install.
Then I just installed Atomic Sway (because not that much bloat), and before logging in rebased to secureblue server-main-userns-hardened. It worked but I have no DNS? Damn…
@Pantherina have you checked if systemd-resolved is working properly and that systemd-networkd or networkmanager is used? only one of them shall be used. i had a similar issue when upgrading from 38 to 39 because then both were active. i’m using NetworkManager on my desktop and disabled systemd-networkd and then it worked…
Strange, Fedora39 to Fedora39, I use that atomic base always (like 15 different installs, GNOME, Plasma6, Secureblue, Cosmic, Sway,…)
@Pantherina
I see. At least systemd-resolved needs to be running and /etc/resolv.conf needs to be 127.0.0.1
I rebooted and now it works. /etc/resolv.conf is not the file you edit, but that localhost DNS is interesting. Saw that a long time ago (Obi wan face)
@Pantherina
Awesome! Great to hear that it works :)
@selfhosted