The ABC of Container-Image Management
summary
When Docker Hub enforces a 200‑pulls per 6‑hour limit, a handful of lines in registries.conf solves CI outages by remapping pulls to other registries via prefix remapping, configuring ordered mirrors and marking local caches as insecure or blocked. The workflow uses Podman/Buildah/CRI‑O for runtime and Skopeo’s skopeo sync to copy dozens to thousands of images into internal registries, which the team deploys quickly and verifies working in production and CI.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:30No One Size Fits All Solutions
- 2:02Red Hat's Swiss Army Knives
- 4:28The Core Building Blocks of Podman and Friends
- 6:04Pulling by Short Names
- 8:02Unqualified-Search Registries
- 9:36Improved Short-Name Resolution with Podman v3.0
- 10:32Short-Name Aliasing
- 11:33Configuring a local Container Registry
- 13:21Blocking a Registry, Namespace or Image
- 14:42Mirroring Registries
- 15:39Remapping References - How Podman CI survived Nov 20
- 19:31Drop-in Config Files
- 21:23Takeaway Message - registries.conf
related talks
31mHow to Use Mirroring and Caching to Optimize your Container Registry
48mImproving Container Image Registry Availability with Kube Image Keeper
16mBest Practices for Container Image Promotion Pipelines
26mContainerization crossroads: Experiences-Experiments-Expectations
51mProduction level Docker
15mKeynote: Best Practices In Implementing Container Image Promotion Pipelines
26mContainerization War Stories
33mDocker Container Lifecycles – Problem or Opportunity?