How to Use Mirroring and Caching to Optimize your Container Registry
summary
Shows how to run Docker’s registry image as a pull-through cache (set registry with --proxy-remote-url and point engines with --registry-mirror flag), then demos: Ubuntu pull drops from ~16s to under 2s. Covers private repos (cache must store credentials), limits (mirror only caches pulls, daemon mirror only for Docker Hub), and a safer alternative: a mirror script that pull, re-tag, push and keep a dated backup so mirrors work offline and allow rollbacks.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:58Why containers are awesome
- 5:36Implementation
- 6:27Demonstration
- 10:12Private vs Public
- 13:23Pull from Cache
- 16:33Cons
- 19:01Demo
- 22:51Mirroring
- 24:32Manual mirroring
- 26:08Why mirror
- 28:14Disadvantages
- 30:19Summary
related talks
28mThe ABC of Container-Image Management
15mOptimizing Cache Usage in Docker Builds
16mBest Practices for Container Image Promotion Pipelines
51mProduction level Docker
48mImproving Container Image Registry Availability with Kube Image Keeper
37mCache Me If You Can: P2P Image Sharing in Kubernetes with Spegel
50mFaster builds and slimmer images with Docker multistage builds
39mWhat Information Are Package & Container Registries Hiding from You?