Using Systemd to Ship Container Runtimes. How?
summary
Adds a systemd-sysext build tool to the Flatcar Container Linux SDK and migrates runtime delivery from Torcx to declarative sysext images, producing Docker/containerd sysext images that can be swapped out without rebuilding the OS. Provides a script (the CX bakery build tool) that turns static binaries into installable sysexts in minutes instead of hours, enables shipping Podman and Python as sysexts via butane→ignition, and notes remaining challenges around extension stability and integrity.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 1:52Flatcar Linux features explained
- 3:40System extensions with Butane
- 5:27Live demo of Podman setup
- 7:24Problem with fixed software versions
- 8:26Tool for building system extensions
- 10:12Solution with composable images
- 12:00Example of Docker version switching
- 15:49Troubleshooting the demo
- 17:03Community contributions and Q&A
related talks
09mLightning Talk: Shipping Container Runtimes as Systemd-Sysext Images
33msystemd-sysext in Prod: What We Learned Extending /usr Without a Package Manager
41mReinventing Container Linux for the Wasm Era (and More) with System Extensions
35mA Containerd And Friends Update: What’s New In Runtimes?
14mBuild It Your Way: Modular Pipelines for Bootable Containers
31mSolving All the Problems with systemd
24mcontainerd Packaging: Who Should Ship and How?
33mProject Shipwright: Build Container Images on k8s