CoreOS Demystified – The Specialized OS Powering OpenShift and Containers
summary
Explains that Fedora CoreOS (FCOS) and Red Hat CoreOS (RHCOS) are minimal, immutable OSes for containers with automatic two-week updates and a single-image rollback model (one-image holdback plus a 48-hour window). Describes the update pipeline where a zinc-in agent detects updates and RPMs3 image deployments atomically switch boot entries, the use of coreos-assembler and OSBuild for building images, Podman Desktop’s FCOS VM workflow, layering and image-mode bootable-container images, multi-arch CI (x86_64, aarch64, s390x, ppc64le) and how customization is pushed via MCO.
AI-written summary · about
chapters (14)
- 0:00CoreOS introduction
- 1:07CoreOS origins and history
- 2:53CoreOS features
- 5:26Automatic updates in CoreOS
- 6:32CoreOS testing and releases
- 7:20Fedora vs RHEL CoreOS
- 8:47CoreOS Assembler and CI
- 9:49Customizing CoreOS images
- 13:50Podman OS pipeline
- 15:37CoreOS Image Mode
- 17:05CoreOS layering
- 18:34Simplifying OpenShift builds
- 19:59Contributing to CoreOS
- 22:53Q&A
related talks
48mFedora CoreOS: architectural walkthrough
44mWhat is Red Hat CoreOS?
28mFedora CoreOS - best host for your containers
13mCoreOS is Dead, Long Live CoreOS
52mGetting Started with Fedora CoreOS
57mThe future of container-enabled infrastructure
45mRed Hat CoreOS and OpenShift v4
16mHow to intelligently pack OS in a container image?