System provisioning and bootc, now and the future
summary
A working workflow replaces or reinstalls a cloud VM with a bootc (bootable) container image and extends to bare metal by pushing OCI images to a registry, deriving specialized images via OCI layering and installing with Anaconda and kickstart. Tools shown include bootc-image-builder, bootc install-to-existing-root and factory-reset flows; secrets live outside the container, static IPs configure via kickstart, and OCI images remain easily inspectable. It works for cloud and data‑center testing but agents, partitioning at runtime, and DD/self‑encrypt disk image cases still need polish.
AI-written summary · about
chapters (13)
- 0:00System provisioning intro
- 1:49Cloud to bare metal deploy
- 5:01OCI tooling challenges
- 8:14Cloud image dark matter
- 10:21Kickstart for bare metal
- 14:19Complex provisioning cases
- 17:06OCI images as file systems
- 20:22bootc design history
- 23:57Future bootc and Anaconda
- 27:47Local dev workflows
- 28:37Q&A: Network installs
- 30:25Q&A: Immutable systems
- 32:01Q&A: OCI artifacts
related talks
25mIntroduction to Bootable Containers
23mCreating Ubuntu and Debian container base images, the old and simple way
35mHardening OS Distribution: Verifiable and sealed OS with bootc and composefs
33mOpenShift OS customization as bootable container!
34mTake the Power Back on Your Containers with Flatcar
26mStreamlining SEAPATH Deployment and Management in Electrical Substati...
36mThese bootc are made for mailin'
52mGetting Started with Fedora CoreOS