Take the Power Back on Your Containers with Flatcar
summary
Flatcar boots a minimal OS image (demo spawns instances with qmu) and runs Docker nginx straight away, provisioning via ignition JSON generated from Butane and delivered as cloud user-data; terraform ties ignition to OpenStack or AWS/GCP images. Update-engine polls every ~20–25 minutes and writes releases to A/B partitions with locksmith controlling reboots, enabling safe rollbacks. There is no package manager and releases ship on alpha/beta/stable cadence about every two weeks, demo completes successfully.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:48What is Flatcar
- 5:44Security features
- 7:50Running Flatcar with Docker
- 11:16Provisioning with Ignition
- 14:08Ignition and Butane
- 19:10Cloud deployment
- 23:26Terraform and Flatcar
- 29:35Automatic updates
- 31:42Release channels
- 33:06Q&A
related talks
23mNomad + Flatcar: A Harmonious Marriage of Lightweights
33mMinimal OS, Maximum Impact: Journey To a Flatcar Maintainer
39mDay 1 Lightning Talks
31mPlumbing the Cloud for Containers
35mForeman, Katello and bootable containers
33mThe "what" and "why" of Flatcar Linux, a friendly fork of Container Linux
40mA Maintainer's Odyssey: Time, Technology, and Transformation
48mUnderstanding Container Engines by Demo™