Running your containers in a sane environment
summary
Project Atomic provides a minimal, mostly immutable OS built from RHEL/Fedora RPMs with OSTree-based atomic upgrades and rollbacks, writable only at /var and /etc, plus a Cockpit GUI for per-host container visibility. Integration with cloud-init and Kubernetes is demonstrated: creating a pod, killing its container, and watching kubectl restarts pods automatically. The claim is operational tooling (Atomic host, OSTree, Cockpit, Kubernetes) that makes Docker containers easier to run and recover without hand-editing the host.
AI-written summary · about
chapters (12)
- 0:00Introduction to Atomic
- 0:49Container management challenges
- 2:25Atomic host overview
- 3:45Atomic upgrades and rollbacks
- 5:17Immutability and security
- 5:51Systemd services management
- 6:40Cockpit GUI interface
- 8:06Kubernetes orchestration
- 9:54Cloud-init configuration
- 11:41Project comparisons and Q&A
- 14:11Host philosophy and tooling
- 19:06Demonstration and conclusion
related talks
26mDeploying containers without k8s?
48mFedora CoreOS: architectural walkthrough
45mRed Hat CoreOS and OpenShift v4
33mBootable Containers: An entire OS as a Containerfile
39mMore Than Secure: Containerd + KataContainers as Kubernetes Runtime
44mWhat is Red Hat CoreOS?
37mCRI-O: Under the Hood
37mManaging Containers at Scale with CoreOS and Kubernetes