How OpenShift Builds Container Images
summary
OpenShift moves image builds into build pods that run builder containers (openshift-docker-builder, source-to-image and imagebuilder libraries) so builds run inside containers instead of on a host Docker daemon; the builders assemble images and push them to a registry because CRI lacks Docker’s build/commit API. Consequences: layer cache disappears with container lifetime, retries and redeploys slow because images aren’t on the node, builds run privileged today, configs land in ConfigMaps, and work remains to enable multi-layer and unprivileged builds.
AI-written summary · about
chapters (11)
- 0:00Introduction and overview
- 1:07Kubernetes fundamentals
- 1:39OpenShift build components
- 6:57The build process mechanics
- 8:38Version 3.11 build architecture
- 9:53Transition to OpenShift 4.0
- 10:56New build execution model
- 11:39Challenges and implications
- 13:31Future goals and refinements
- 14:54Q&A and technical discussion
- 17:37Conclusion
related talks
15mRunning Multi-Arch Builds & Tests in OpenShift CI/CD
34mUnprivileged Image Builds: What are the Challenges and Where are we Today?
38mRunning Multi-Arch Builds & Tests in OpenShift CI/CD
45mOpenShift the power of Kubernetes for developers
33mDocker Container Lifecycles – Problem or Opportunity?
35mBuilding Container Images In Kubernetes: It’s Been a Journey!
01h 06mOpenShift - the power of Kubernetes for engineers
33mOpenShift OS customization as bootable container!