New stable Fedora CoreOS release available: 43.20260105.3.0
https://www.fedoraproject.org/coreos/release-notes?arch=x86_64&stream=stable
New stable Fedora CoreOS release available: 43.20260105.3.0
https://www.fedoraproject.org/coreos/release-notes?arch=x86_64&stream=stable
Major learning curve to use #fedora #coreos is how to create ignition file. #FCOS installation use that for installation configuration. There's no menu or wizard like other #linux distros.
Why? Because one of major goal of #FCOS is to enable easy mass deployment of similar configuration.
After you learn and solved that problem, remaining else is just systemd and #podman #quadlet (most #fcos deployment is to run containerized applications)
@zrail I've managed some #fedora #coreos to run dozens of #podman container. Works nicely.
I can depend zincati to auto-update os, and podman-auto-update systemd service to update container isafely. #fcos update is atomic update.
No need to doing manual major distro upgrade because zincati take care of that.
Yes, u should monitor memory usage. You can run #promotheus & grafana container to monitor it. Also there is prometheus-podman-exporter to monitor podman container with prometheus easily.
@aku dibilang distro-hopping jg gak om.. itu2 aja kan.. kalo skrg ya intinya workstation #fedora, server ya #rhel clone kayak #almalinux atau #rockylinux, kombinasi dikit sama #fcos (fedora coreos). Ada juga opensuse tumbleweed. Tp itu semua kan bisa dibilang satu aliran
I figured out how to make a Fedora CoreOS template for XCP-ng that supports unattended installs by supplying an ignition file through Xen Orchestra's cloud config templates!
Now, #fedora is still my daily OS on my workstation (PC and laptop). On my servers, #centos had been my primary server distro, but changed to #rockylinux and #almalinux because #redhat policy changes.
There are some of my servers also use fedora #coreos aka #fcos and i love it.
Also touch #ubuntu or #debian, but only because some of my company's customer use that on their servers.
Also touch debian because it is base distro of #proxmox VE and #raspberry #pi #raspbian.
@Wiulinu I recommend #fedora coreos for #homeserver
Fedora CoreOS 43 Test Days are happening from Sep 22-26!
There will be a virtual session for folks to ask questions on Monday September 22 from 10:00 AM - 11:30 AM EDT (2:00 PM - 3:30PM UTC).
Consider helping out if you're able. :)
➡️ https://discussion.fedoraproject.org/t/test-day-fedora-coreos-43-test-week/164457
Had a uncomfortably large aha moment when I realized that, based on the way #fcos / #ucore works, I don't have to tear down and rebuild the VM to update configurations on everything, but instead define my own OCI/ostree image to load all my container configuration.
I've literally been destroying and rebuilding the image every time I've wanted to make a config change, or add a new service to the homelab. :neobread_facepalm:
Only seeing a notice in the monitoring that fedora core os has updated to a new major version and everything just works is pretty satisfying...
#fcos #fedoracoreos
Running Fedora CoreOS (FCOS) on Hetzner Cloud :fedora: with a custom image and Ignition via user-data :-)
How To:
https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-hetzner/
Help us test Fedora CoreOS 42 from today to Friday, Mar 24-28!
➡️ https://fedoramagazine.org/contribute-at-the-fedora-42-coreos-test-week/
@x_cli Si tu utilises LUKS avec Clevis (TPM2) sur FCOS et que tu dois effacer le volume, c'est probablement dû à l'option wipe_volume: true par défaut. Ça empêche de garder les données entre les installs. Pour éviter ça, configure LUKS manuellement sans cette directive et assure-toi que Clevis ajoute une nouvelle keyslot sans écraser l'existant. 🚀 #Linux #LUKS #FCOS
So I tried to use LUKS parts on #FCOS with a clevis binding to the TPM2. I get an error if I don't wipe the volume.
This prevents me from keeping the data between installations. Is it normal or am I missing something here?
PSA on Fedora CoreOS cloud uploads that will be getting pruned. These are for uploads that are older than two years.
If you're using one of these versions, please consider updating!
➡️ https://discussion.fedoraproject.org/t/starting-to-prune-fedora-coreos-cloud-images/138927
Help us test Fedora IoT and Fedora CoreOS for the release of Fedora 41!
If you're familiar with Fedora Atomic Desktops, then these editions will not seem so different aside from the server use case.
Both test days are running from today, Oct 7 to Friday, Oct 11.
More details on how to participate: https://fedoramagazine.org/contribute-at-fedora-coreos-and-iot-test-week/
#Fedora #FedoraIoT #FedoraCoreOS #FCOS #FedoraAtomic #Linux #OpenSource
Does anyone know how I can create the BIOS boot, and EFI partitions using a #FCOS ignition'/butane file? I can't seem to figure out how to do it :(
Deuxième volet de l'aventure Fedora CoreOS (#FCOS) sur #Proxmox : détails techniques sur la preuve de concept pour la création d'une machine virtuelle d'installation :
https://broken-by-design.fr/posts/proxmox-fcos2/
Dans ce second billet, on tape dans le dur : les défis techniques rencontrés, la publication du code source #Opentofu #Terraform, avec des bouts de #systemd et de #SELinux dedans, sans compter un peu de kung-fu de conteneurs #podman #docker
Grosse semaine de taf pour écrire et debug tout ça.