home.social

#fcos — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fcos, aggregated by home.social.

  1. @cichy1173 welcome to #fcos fan club. I use FCOS a lot both on my #homelab and my corporate systems.

    For me, the combination of FCOS and #containers (using #podman #quadlet) workload is the most stable and easy way to get up-to-date system. You can depend on FCOS's zincati and podman-auto-update timer to get up-to-date systems in easy but stable.

  2. @cichy1173 welcome to #fcos fan club. I use FCOS a lot both on my #homelab and my corporate systems.

    For me, the combination of FCOS and #containers (using #podman #quadlet) workload is the most stable and easy way to get up-to-date system. You can depend on FCOS's zincati and podman-auto-update timer to get up-to-date systems in easy but stable.

  3. @cichy1173 welcome to #fcos fan club. I use FCOS a lot both on my #homelab and my corporate systems.

    For me, the combination of FCOS and #containers (using #podman #quadlet) workload is the most stable and easy way to get up-to-date system. You can depend on FCOS's zincati and podman-auto-update timer to get up-to-date systems in easy but stable.

  4. @cichy1173 welcome to #fcos fan club. I use FCOS a lot both on my #homelab and my corporate systems.

    For me, the combination of FCOS and #containers (using #podman #quadlet) workload is the most stable and easy way to get up-to-date system. You can depend on FCOS's zincati and podman-auto-update timer to get up-to-date systems in easy but stable.

  5. Fedora had released Fedora CoreOS 43.20260413.3.2 on "stable stream" few hours ago to patch against Copy Fail.

    Upgraded packages:

    • kernel-6.19.11-200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64
    • kernel-core-6.19.11-200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64
    • kernel-modules-6.19.11-- 200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64
    • kernel-modules-core-6.19.11-200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64

    You can wait your zincati service schedule to upgrade automatically, or you can run sudo zincati-update-now to upgrade immediately.

    #copyfail #fedora #fcos #coreos

  6. Fedora had released Fedora CoreOS 43.20260413.3.2 on "stable stream" few hours ago to patch against Copy Fail.

    Upgraded packages:

    • kernel-6.19.11-200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64
    • kernel-core-6.19.11-200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64
    • kernel-modules-6.19.11-- 200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64
    • kernel-modules-core-6.19.11-200.fc43.x86_64 ⟶ 6.19.12-200.fc43.x86_64

    You can wait your zincati service schedule to upgrade automatically, or you can run sudo zincati-update-now to upgrade immediately.

    #copyfail #fedora #fcos #coreos

  7. Rolling-out zincati-update-now to update our Fedora CoreOS instances immediately and tackle copyfail.

    #copyfail #fedora #coreos #fcos #zincati

  8. Rolling-out zincati-update-now to update our Fedora CoreOS instances immediately and tackle copyfail.

    #copyfail #fedora #coreos #fcos #zincati

  9. @ercanbrack I can confirm this. Checked on my #Fedora 43 workstation.

    But I'm still waiting for the next update of Fedora #CoreOS / #fcos.

  10. @ercanbrack I can confirm this. Checked on my #Fedora 43 workstation.

    But I'm still waiting for the next update of Fedora #CoreOS / #fcos.

  11. @ercanbrack I can confirm this. Checked on my #Fedora 43 workstation.

    But I'm still waiting for the next update of Fedora #CoreOS / #fcos.

  12. @ercanbrack I can confirm this. Checked on my #Fedora 43 workstation.

    But I'm still waiting for the next update of Fedora #CoreOS / #fcos.

  13. 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)

  14. 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)

  15. 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)

  16. 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)

  17. @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.

  18. @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.

  19. @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.

  20. @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.

  21. 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!

    lethedata.com/blog/xo_fcos_tem

    #fedora #fcos #xcpng #xo

  22. 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.

  23. 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.

  24. 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.

  25. 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.

  26. 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. :)

    ➡️ discussion.fedoraproject.org/t

  27. 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. :)

    ➡️ discussion.fedoraproject.org/t

    #Fedora #FCOS #FedoraCoreOS #Linux #OpenSource

  28. 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. :)

    ➡️ discussion.fedoraproject.org/t

    #Fedora #FCOS #FedoraCoreOS #Linux #OpenSource

  29. 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. :)

    ➡️ discussion.fedoraproject.org/t

    #Fedora #FCOS #FedoraCoreOS #Linux #OpenSource

  30. 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. :)

    ➡️ discussion.fedoraproject.org/t

    #Fedora #FCOS #FedoraCoreOS #Linux #OpenSource

  31. 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:

  32. 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:

  33. Running Fedora CoreOS (FCOS) on Hetzner Cloud :fedora: with a custom image and Ignition via user-data :-)

    How To:
    docs.fedoraproject.org/en-US/f

    #linux #fedora #coreos #fcos

  34. @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

  35. 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!

    ➡️ discussion.fedoraproject.org/t

  36. 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!

    ➡️ discussion.fedoraproject.org/t

    #CoreOS #Fedora #FedoraCoreOS #FCOS #Linux #OpenSource

  37. 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!

    ➡️ discussion.fedoraproject.org/t

    #CoreOS #Fedora #FedoraCoreOS #FCOS #Linux #OpenSource

  38. 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!

    ➡️ discussion.fedoraproject.org/t

    #CoreOS #Fedora #FedoraCoreOS #FCOS #Linux #OpenSource

  39. 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!

    ➡️ discussion.fedoraproject.org/t

    #CoreOS #Fedora #FedoraCoreOS #FCOS #Linux #OpenSource

  40. 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: fedoramagazine.org/contribute-

  41. 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: fedoramagazine.org/contribute-

    #Fedora #FedoraIoT #FedoraCoreOS #FCOS #FedoraAtomic #Linux #OpenSource

  42. 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: fedoramagazine.org/contribute-

    #Fedora #FedoraIoT #FedoraCoreOS #FCOS #FedoraAtomic #Linux #OpenSource

  43. 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: fedoramagazine.org/contribute-

    #Fedora #FedoraIoT #FedoraCoreOS #FCOS #FedoraAtomic #Linux #OpenSource