Keynote: Best Practices In Implementing Container Image Promotion Pipelines
summary
Rebuilding Docker images is rarely deterministic, so the recommended approach is to build once and promote immutable artifacts using checksum-backed storage. Use per-environment registries (local, test, staging, prod) plus a virtual registry for unified access and proxy caches for Docker Hub to avoid throttling. Promotion occurs via API/CLI (no re-download re-upload) so moving an image just flips visibility. Example stack: JFrog Artifactory / JFrog Container Registry and JFrog CLI; this yields immediate, reliable promotions and reproducible production images.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:30Disclaimer
- 1:04Introduction
- 2:50Promotion Pipelines
- 8:00Solution
- 10:36Docker Limitations
- 11:20Promotion Pipeline
related talks
40mBest Practices In Implementing Container Image Promotion Pipelines- 40mBest Practices In Implementing Container Image Promotion Pipelines
16mBest Practices for Container Image Promotion Pipelines
41mDocker Container Lifecycles, problem or opportunity?
33mDocker Container Lifecycles – Problem or Opportunity?
31mBuilding a private CI/CD pipeline with Java and Docker in the Cloud
49mContinuous Delivery at Docker age
51mProduction level Docker