home.social

#flatcar — Public Fediverse posts

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

fetched live
  1. The #Flatcar booth at #FrOSCon is set up and eagerly awaits your visit on Saturday and on Sunday.

    We're conveniently located on the left when entering the project booths / food area, right next to our #Gentoo upstream.

    The booth features a projector screen for ad-hoc demos and for interactively exploring Flatcar with you. Hop over and say hi!

    (We speak Englisch, wir sprechen Deutsch, mówimy po Polsku.)

    Please boost :boost_requested: !

    #Container #ContainerLinux #Kubernetes #FrOSCon2026

  2. The #Flatcar booth at #FrOSCon is set up and eagerly awaits your visit on Saturday and on Sunday.

    We're conveniently located on the left when entering the project booths / food area, right next to our #Gentoo upstream.

    The booth features a projector screen for ad-hoc demos and for interactively exploring Flatcar with you. Hop over and say hi!

    (We speak Englisch, wir sprechen Deutsch, mówimy po Polsku.)

    Please boost :boost_requested: !

    #Container #ContainerLinux #Kubernetes #FrOSCon2026

  3. #LT View the complete release notes and download the latest Flatcar releases on our (awesomely refactored) release page:

    flatcar.org/releases

    #Flatcar #ContainerLinux #CloudNative #Linux

  4. #LT View the complete release notes and download the latest Flatcar releases on our (awesomely refactored) release page:

    flatcar.org/releases

    #Flatcar #ContainerLinux #CloudNative #Linux

  5. @whitequark Both "about 5 bucks" and " significantly more than 15 bucks"; the former for personal use and the latter for #Flatcar CI which I'm a maintainer of. CI-ing a Linux distro takes some resources...

  6. @whitequark Both "about 5 bucks" and " significantly more than 15 bucks"; the former for personal use and the latter for #Flatcar CI which I'm a maintainer of. CI-ing a Linux distro takes some resources...

  7. Digital Sovereignty isn't just for nations!

    Now that the desktop has reached The Final Shape we turn attention to our homelabs.

    Been making great progress on this, we're at v .8. This one is boring. Knuckle just installs flatcar.

    But we want cloud native magic so we're building "Bluefin Server" but not sure on the name. And it'll run flatcar, and in there your magical bootc factory runs and your bluebuild just worked ootb. And the Fedora one will come with coreOS, tekton, forgejo, konflux, etc.

    A place for both - if we design the homeserver and desktop as one unified WHOLE, we could do a ton more stuff. The tech is already finished.

    #linux #coreos #flatcar #gentoo

    docs.projectbluefin.io/blog/in

  8. Digital Sovereignty isn't just for nations!

    Now that the desktop has reached The Final Shape we turn attention to our homelabs.

    Been making great progress on this, we're at v .8. This one is boring. Knuckle just installs flatcar.

    But we want cloud native magic so we're building "Bluefin Server" but not sure on the name. And it'll run flatcar, and in there your magical bootc factory runs and your bluebuild just worked ootb. And the Fedora one will come with coreOS, tekton, forgejo, konflux, etc.

    A place for both - if we design the homeserver and desktop as one unified WHOLE, we could do a ton more stuff. The tech is already finished.

    #linux #coreos #flatcar #gentoo

    docs.projectbluefin.io/blog/in

  9. RE: mastodon.social/@sjvn/11660166

    Awesome to see #flatcar #linux get a commercial product. Hope to see more! Congrats @thilo and co!

    Before I worked with the bootc team to get that into the @cloudnativefdn I worked with the team at MS to get flatcar into the CNCF!

    It took a year (paperwork sucks). Awesome server os, I'm working on something slick for you all who wanna try it at home.

  10. RE: mastodon.social/@sjvn/11660166

    Awesome to see #flatcar #linux get a commercial product. Hope to see more! Congrats @thilo and co!

    Before I worked with the bootc team to get that into the @cloudnativefdn I worked with the team at MS to get flatcar into the CNCF!

    It took a year (paperwork sucks). Awesome server os, I'm working on something slick for you all who wanna try it at home.

  11. If you’re in Prague this weekend and care about practical Linux ops, I’m doing two talks at Installfest.cz on Saturday (building A, CTU FEL, Karlovo náměstí), both in English:

    15:30–15:55 (Track II) – You Don’t Need Kubernetes: Side Projects on One Linux Server

    17:00–17:25 (Track III) – Flatcar Linux 101: A Hands-Free Server OS

    Details:
    pretalx.installfest.cz/install

    pretalx.installfest.cz/install

    #Installfest #Flatcar #PuzzleSecretary

  12. If you’re in Prague this weekend and care about practical Linux ops, I’m doing two talks at Installfest.cz on Saturday (building A, CTU FEL, Karlovo náměstí), both in English:

    15:30–15:55 (Track II) – You Don’t Need Kubernetes: Side Projects on One Linux Server

    17:00–17:25 (Track III) – Flatcar Linux 101: A Hands-Free Server OS

    Details:
    pretalx.installfest.cz/install

    pretalx.installfest.cz/install

    #Installfest #Flatcar #PuzzleSecretary

  13. @Foxboron (and for a chat at KubeCon, drop by the #Flatcar booth at the Project pavilion - we're there every KubeCon day in the afternoon)

  14. @Foxboron (and for a chat at KubeCon, drop by the #Flatcar booth at the Project pavilion - we're there every KubeCon day in the afternoon)

  15. For a fireside chat with creators and maintainers of #SpecialPurposeOS #Linux distributions like #Flatcar or #Kairos at #FOSDEM, please drop by our SPOS BOF Session: Today (Saturday) 5pm in K4.401.

    No matter whether you're curious, a user, or a maintainer - drop by and join us!

    (Also, please boost!)
    fosdem.org/2026/schedule/event

  16. For a fireside chat with creators and maintainers of #SpecialPurposeOS #Linux distributions like #Flatcar or #Kairos at #FOSDEM, please drop by our SPOS BOF Session: Today (Saturday) 5pm in K4.401.

    No matter whether you're curious, a user, or a maintainer - drop by and join us!

    (Also, please boost!)
    fosdem.org/2026/schedule/event

  17. 🚨 All channels include critical fixes for runc vulnerabilities -
    CVE-2025-31133, CVE-2025-52565, CVE-2025-52881. Update soon to stay safe!
    #Flatcar #Security #runc

  18. 🚨 All channels include critical fixes for runc vulnerabilities -
    CVE-2025-31133, CVE-2025-52565, CVE-2025-52881. Update soon to stay safe!
    #Flatcar #Security #runc

  19. 🌅 New day, new Flatcar releases!

    Alpha 4515.0.0, Beta 4459.1.1, and Stable 4459.2.0 are out with Linux 6.12.54, cgroups v1 kernel config mitigations, and major security updates across the stack.

    #Flatcar #Linux #ContainerLinux

  20. 🌅 New day, new Flatcar releases!

    Alpha 4515.0.0, Beta 4459.1.1, and Stable 4459.2.0 are out with Linux 6.12.54, cgroups v1 kernel config mitigations, and major security updates across the stack.

    #Flatcar #Linux #ContainerLinux

  21. I rarely talk about work here, but this took quite some effort of the team and fellow maintainers:

    pixelrobots.co.uk/2025/11/flat

    Today, we add #Azure #AKS to our list of hosted #Kubernetes offers that support #Flatcar #Container #Linux. It's not the first, and it sure won't be the last. Documentation is here: learn.microsoft.com/en-us/azur

  22. I rarely talk about work here, but this took quite some effort of the team and fellow maintainers:

    pixelrobots.co.uk/2025/11/flat

    Today, we add #Azure #AKS to our list of hosted #Kubernetes offers that support #Flatcar #Container #Linux. It's not the first, and it sure won't be the last. Documentation is here: learn.microsoft.com/en-us/azur

  23. 859 contributions to 6 repositories, says my #CNCF Contributor card

    And the whole journey started with a contribution to #Flatcar, thanks to @thilo

    contribcard.cncf.io/jasonbraga

  24. 859 contributions to 6 repositories, says my #CNCF Contributor card

    And the whole journey started with a contribution to #Flatcar, thanks to @thilo

    contribcard.cncf.io/jasonbraga

  25. Spent some time thinking about a #DevOps flow for agency-sized orgs working on web applications.

    The idea is using #nix to pack a reproducible dev environment and build a docker image from it, which will be deployed on a container-host OS like #flatcar .

    Principles:
    - must be usable for small-sized projects on private infra or cloud providers
    - must be development-first, so 1:1 parity between a local environment and production and no DevOps gates during deployments
    - everything outside the dev env should be minimally intrusive
    - OSS and lightweight sw is preferred

    Locally we would have a nix-shell with runtime, toolchain (dependency managers and such) and a webserver. Also obv the app's git repo.
    Then we would have a *build node* that acts as a docker registry and an online dev env. A simple pipeline would:
    - pull the git repo
    - build the docker image with nix
    - push it to the local docker registry
    - run the image and serve it.
    This is automatable in a number of ways, including Ansible straight from the dev's machine without external CI tools.

    The *prod node* would leverage Flatcar's init system to pull the latest the docker image and run it at boot, the provisioning can be done manually or via Terraform.

    All testing (including security) runs in the dev environment.
    Environment variables are also managed inside the application (with something like dotenvx) with appropriate secret management, keeping in mind that every build is a prod build, and all else is dev.

    Database and observability systems are to be considered external dedicated services. Static assets (like media files) on the prod node are stored in a volume keeping the same paths as dev's.
    Basic status-based orchestration can be done in docker leveraging healthchecks.

  26. Spent some time thinking about a #DevOps flow for agency-sized orgs working on web applications.

    The idea is using #nix to pack a reproducible dev environment and build a docker image from it, which will be deployed on a container-host OS like #flatcar .

    Principles:
    - must be usable for small-sized projects on private infra or cloud providers
    - must be development-first, so 1:1 parity between a local environment and production and no DevOps gates during deployments
    - everything outside the dev env should be minimally intrusive
    - OSS and lightweight sw is preferred

    Locally we would have a nix-shell with runtime, toolchain (dependency managers and such) and a webserver. Also obv the app's git repo.
    Then we would have a *build node* that acts as a docker registry and an online dev env. A simple pipeline would:
    - pull the git repo
    - build the docker image with nix
    - push it to the local docker registry
    - run the image and serve it.
    This is automatable in a number of ways, including Ansible straight from the dev's machine without external CI tools.

    The *prod node* would leverage Flatcar's init system to pull the latest the docker image and run it at boot, the provisioning can be done manually or via Terraform.

    All testing (including security) runs in the dev environment.
    Environment variables are also managed inside the application (with something like dotenvx) with appropriate secret management, keeping in mind that every build is a prod build, and all else is dev.

    Database and observability systems are to be considered external dedicated services. Static assets (like media files) on the prod node are stored in a volume keeping the same paths as dev's.
    Basic status-based orchestration can be done in docker leveraging healthchecks.

  27. Okay, creating a custom unit that runs `systemctl enable podman.socket` after basic.target fixes it (I guess that supports my theory that it’s sysext-related). I’m wondering though if this is the best solution, or if I’m missing something obvious. #Flatcar #devops #homelab #selfhosting

  28. Okay, creating a custom unit that runs `systemctl enable podman.socket` after basic.target fixes it (I guess that supports my theory that it’s sysext-related). I’m wondering though if this is the best solution, or if I’m missing something obvious. #Flatcar #devops #homelab #selfhosting

  29. Trying to migrate from Fedora CoreOS to #Flatcar, but having a hard time getting the Podman-related systemd units enabled in my Butane config. In FCOS, setting `enabled` to true was sufficient. The same doesn’t seem to work with Flatcar. qemu-guest-agent.service works though. So I’m wondering if the reason might be that Podman is a sysext and therefore not available early enough? #devops #homelab #selfhosting

  30. Trying to migrate from Fedora CoreOS to #Flatcar, but having a hard time getting the Podman-related systemd units enabled in my Butane config. In FCOS, setting `enabled` to true was sufficient. The same doesn’t seem to work with Flatcar. qemu-guest-agent.service works though. So I’m wondering if the reason might be that Podman is a sysext and therefore not available early enough? #devops #homelab #selfhosting

  31. Calm before the conference. If you're at #FrOSCon check out the Flatcar booth right at the Mensa, next to #KairOS and near #Fedora #CoreOS.

    I have a #Kubernetes #Sysext talk on #Flatcar #container #linux at 6 tomorrow, and @tormath1 will follow up with a hands-on tutorial on Sunday at 4.

  32. Calm before the conference. If you're at #FrOSCon check out the Flatcar booth right at the Mensa, next to #KairOS and near #Fedora #CoreOS.

    I have a #Kubernetes #Sysext talk on #Flatcar #container #linux at 6 tomorrow, and @tormath1 will follow up with a hands-on tutorial on Sunday at 4.

  33. Attending to #FrOSCon this year is a good opportunity to: learn about Flatcar and discuss your use-cases with some Flatcar's maintainers (at the Flatcar booth and/or during the social event). See you there! #systemd #sysext #linux #flatcar #OpenSource #DevOps

  34. Attending to @FrOSCon this year is a good opportunity to: learn about Flatcar and discuss your use-cases with some Flatcar's maintainers (at the Flatcar booth and/or during the social event). See you there!

    #systemd #sysext #linux #flatcar #OpenSource #DevOps

  35. Attending to @FrOSCon this year is a good opportunity to: learn about Flatcar and discuss your use-cases with some Flatcar's maintainers (at the Flatcar booth and/or during the social event). See you there!

    #systemd #sysext #linux #flatcar #OpenSource #DevOps

  36. They even use maintenance windows to stay up to date and automatically install new #Flatcar releases! Good stuff.

    github.com/jakelmg/flatcar-lan

  37. They even use maintenance windows to stay up to date and automatically install new #Flatcar releases! Good stuff.

    github.com/jakelmg/flatcar-lan