Nomad + Flatcar: A Harmonious Marriage of Lightweights
summary
Flatcar Container Linux pairs with Nomad as a minimal, secure host: immutable root /usr partition prevents container escape like the runc overwrite exploit, and Flatcar provides auto-updating, atomic rollbacks with images on public clouds. Provisioning uses Ignition + Container Linux Config + ct to bake Nomad by downloading the official zip, verifying its hash, and placing the binary under /opt/bin via a systemd unit. The uploader shows a working Azure cluster (demo app lands on node07), but operationally missing is coordinated update orchestration — use locksmith update coordination or a Nomad operator to drain nodes before reboot.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:40Understanding Flatcar
- 5:32Flatcar architecture
- 7:33Nomad and Flatcar synergy
- 8:24Configuration with Ignition
- 11:46Installing Nomad on Flatcar
- 13:46Update orchestration
- 16:48Technical demonstration
- 22:10Resources and conclusion
related talks
12mNomad: Lightweight Orchestration That Complements Kubernetes
34mTake the Power Back on Your Containers with Flatcar
24mUnlocking Cloud-Native Efficiency: A Journey with Flatcar
53mBootiful workload orchestration with Hashicorp Nomad
38mContainer Linux: The Next 10 Years
33mMinimal OS, Maximum Impact: Journey To a Flatcar Maintainer
33mThe "what" and "why" of Flatcar Linux, a friendly fork of Container Linux
27mIntro: Virtual Kubelet