Container Linux: The Next 10 Years
summary
Flatcar adopts system extensions (sysexts) to layer packages like containerd, Docker and multiple Kubernetes runtimes as immutable overlays, with a bakery hosting CSX images and a systemd-based supdate service that stages updates and writes a reboot_required marker. The demo shows Kubernetes sysexts updating node-by-node and versions switching after coordinated reboots orchestrated with qd, enabling in-place CAPI upgrades and optional Wasm runtime images; Flatcar is now a CNCF project.
AI-written summary · about
chapters (9)
- 0:00What is Container Linux
- 3:51CoreOS legacy and impact
- 5:56Evolving distribution model
- 12:00Demo of system extensions
- 18:37Cluster API with system extensions
- 24:46Security in the next decade
- 29:04Next-gen workloads and WASM
- 33:17Key themes and takeaways
- 34:02Q&A session
related talks
33msystemd-sysext in Prod: What We Learned Extending /usr Without a Package Manager
30mContainers and Next Gen Infrastructure Ecosystem
05mBare Metal to Containers to K8s: How We Got Here
23mNomad + Flatcar: A Harmonious Marriage of Lightweights
29mUnderstanding the Container Revolution
05mWhat's Exciting Now In Bootc, And What's Next?
25mRelease the Kraken: Bring Sidecar Containers to Next Level
33mBootable Containers: An entire OS as a Containerfile