Best Practices in Docker Continuous Delivery
summary
Riot Games’ CI pipeline builds slim images (Go on Alpine producing 15–20MB images), pins official base tags, and promotes validated artifacts from a noisy dev repo into a separate prod repo instead of rebuilding. Images are stored in Artifactory and pushed to global sites using Artifactory multi-push replication; that reduces pull latency but revealed network and garbage‑collection pain once the registry grows (~125,000 images), so automated TTL cleanup and Jenkins-driven dependency rebuilds are used.
AI-written summary · about
chapters (27)
- 0:00Intro
- 0:55AGENDA -Containers and images
- 1:54CONTAINERS & IMAGES
- 2:24CONTAINERS ENCAPSULATE
- 3:16CONTAINERS ARE FUNCTIONAL
- 4:00IMAGES ARE LIKE ONIONS
- 5:30IMAGES GO INTO REGISTRIES
- 6:25IMAGES MAKE CONTAINERS
- 7:11ORGANIZING CONTAINERS
- 8:54MICROSERVICE VS APPLIANCE
- 9:46MICROSERVICE CONTAINERS
- 10:57APPLIANCE CONTAINERS
- 11:38CRAFTING IMAGES
- 14:08WHY? SECURITY
- 17:15SELECT A BASE
- 19:08SUGGESTED BASES
- 22:16BUILD YOUR OWN BASE
- 23:12SHARE YOUR BASES
- 26:03CONSOLIDATE LAYERS
- 29:02DELIVERING IMAGES
- 30:46INTERNAL REGISTRY
- 32:01SOURCE OF TRUTH
- 33:34LOGICAL REPOS
- 35:23TEAM PERMISSIONS
- 39:37DISTRIBUTING IMAGES
- 40:35MULTIPUSH REPLICATION IS SWEET
- 41:12REPLICATE ONLY PROD REPO
related talks
16mBest Practices for Container Image Promotion Pipelines
27mOptimizing CI/CD Pipelines for Faster Time to Market
01h 09mDocker in Production
48mHow to build solid CI-CD pipeline
40mBest Practices In Implementing Container Image Promotion Pipelines
49mContinuous Delivery at Docker age
51mProduction level Docker
31mBuilding a private CI/CD pipeline with Java and Docker in the Cloud