The Triangle of Compromises: Podman Quadlets Solve the Industrial Edge Dilemma
summary
Industrial edge use cases for 256 MB–1 GB devices get a concrete alternative: Podman Quadlets run OCI containers as systemd services with a 16-line .container file that enables kernel watchdog, cgroups v2 limits, seccomp/SELinux and automatic recovery under PID 1. Live Raspberry Pi demos show a Quadlet deployment from scratch, WebAssembly via crun, and Compose-to-Quadlet conversion using podlet. Claimed benefits are no daemon, no orchestrator, zero runtime overhead and a proposed quadlet.v1 Margo spec for fleet management.
AI-written summary · about
chapters (15)
- 0:00Industrial edge dilemma
- 1:49Kubernetes not viable
- 3:57Key criteria for solutions
- 7:27Packages vs compose vs K8s
- 8:56Podman Quadlets game changer
- 10:23Network and hardware limits
- 13:11Margo specification
- 15:00Rejected packages and K8s
- 16:51Security benefits of Quadlets
- 17:53Scaling with Quadlets
- 19:02Integration with fleet managers
- 20:49Certificates and provisioning
- 22:20Cybersecurity at boot
- 23:48Quadlets niche in industry
- 25:14Closing thoughts
related talks
37mContainer life cycle management in Automotive/Edge deployments.
40mContainers in a Car
36mPaving the Way for Uninterrupted Car Operations
37mBoF: Challenges of Low Spec Embedded Linux
40mCase Study for Resource Control in Embedded Linux Container Integration
38mThe Internet of Things and Life Beyond Linux
37mEmbedded Containers as a Deployment Component via the Yocto Project
38mMicroservices running natively on ARM devices