Podman, Buildah, Skopeo, and CRI-O A Year Later
summary
Updates across the container suite show concrete changes: Buildah supports fully isolated builds with buildah from-scratch, encourages minimal images and demonstrates a measurable tradeoff between isolation (slower) and mounted-cache performance (faster); Podman adds podman generate kube and podman generate systemd to export running containers to Kubernetes YAML or systemd units; Skopeo now performs registry-to-registry transfers including cross-arch copies via skopeo copy; CRI-O becomes the OpenShift runtime with mirror support, read-only defaults and work-in-progress removal of the infra container.
AI-written summary · about
chapters (11)
- 0:00Intro
- 3:31Buildah
- 8:50Buildah Security
- 10:24Buildah in Openshift
- 14:57Podman
- 19:04Podman Demo
- 23:34SystemD Demo
- 27:09Scope Demo
- 28:52Cryo Demo
- 32:44Inference Container
- 39:02Resources
related talks
43mContainer Security: So Many Options, Use Them All!
39mReplacing Docker with Podman
39mPodman - create, run and secure Linux containers
34mWhat Container Runtime Engine Do I Need?
30mRootless, Reproducible, and Hermetic: Secure Container Build Showdown
44mWhale and Seal, Two Playful Friends (Docker and PodMan)
24mOCI, CRI, ??: Making Sense of the Container Runtime Landscape in Kubernetes
36mKata Containers: Hypervisor-Based Container Runtime