t-lo

3 ms·

1.
by t-lo 3y ago
It requires a tiny bit of messing around but yes, Flatcar runs on RPi. It's part of our docs; here's the howto: https://www.flatcar.org/docs/latest/installing/bare-metal/ra...
2.
by t-lo 3y ago
It's a distro to run containers on. It is configured declaratively before deployment, so there's no config drift. It's fully automatable and the OS is self-updating (atomically, including automated roll-backs to known-good st
3.
by t-lo 3y ago
Thanks for the feedback :) Apparently there's always room to improve our docs. A maintainer has taken a stab on that (see https://github.com/flatcar/flatcar-website/pull/263 for progress) and we'll
4.
by t-lo 3y ago
As Flatcar is a very minimal, immutable distribution to run containers / Kubernetes, our development environment (aka the "Flatcar SDK") is containerised too. Flatcar releases are tied to git commits in our distro automation
5.
by t-lo 3y ago
Infrastructure using cloud-init is under risk of suffering from config drift. Cloud-init runs at (each) boot while ignition runs once, at provisioning time. The benefit is reproducible deployments: Any deployment of a given configuration wi
6.
by t-lo 3y ago
For more on immutable / image-based Linux you might want to check out the UAPI group, a recently founded cross-distro interest group: https://uapi-group.org/ We have contributing members from many FOSS projects gravita
7.
by t-lo 3y ago
The most significant change this acquisition brought to Flatcar was to turn it from a vendor-driven open source project to a community-driven one. Also see Kinvolk's statement at the time: https://kinvolk.io/blog/2