Lightning Talk: Shipping Container Runtimes as Systemd-Sysext Images
summary
Adds a systemd-sysext build path into the Flatcar Container Linux SDK and migrates runtime delivery from Torcx to a reproducible build_sysext script that preserves package metadata and Portage config so Flatcar-specific sysexts can be built. Produces Docker sysext images (Docker and containerd static binaries plus systemd units) as squashfs/ext4 images without loop mounts, integrates ignition-generated updates, and is already used to build OEM images (Azure) and to fetch runtime image updates from hosted locations.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:43Background
- 2:00FlatCar
- 2:25SystemdSysext
- 4:10CSX
- 4:59Ignition
- 6:02How is this useful
- 6:39Updates
related talks
18mUsing Systemd to Ship Container Runtimes. How?
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
33mThe "what" and "why" of Flatcar Linux, a friendly fork of Container Linux
05mLightning Talk: Scaling Container Builds with Software Supply Chains
39mDay 1 Lightning Talks
34mTake the Power Back on Your Containers with Flatcar
09mLightning Talk: What’s Inside Your Container Image? How to Audit All the Dependencies...