Best Practices for Container Image Promotion Pipelines
summary
Argues that Dockerfiles should not be rebuilt at each stage but build once and promote the exact image through quality gates; shows Docker build causes non‑reproducible images, labels and repos don’t enforce isolation, and HTTP proxy hacks are brittle. Demonstrates using a Jeffro container registry (local registries backed by shared storage, virtual repos and remote caches) to promote via a REST API instead of pull‑retag‑push, to isolate environments and own dependencies, with immediate promotions and working cache of base images.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 1:25About the speaker and resources
- 2:50Promotion pipelines concept
- 4:36Why Docker promotion is tricky
- 7:48Build once promote approach
- 9:16Labeling and repositories limits
- 11:49Solutions for registry isolation
- 13:59Virtual registry benefits
- 15:00Conclusion and Q&A
related talks
40mBest Practices In Implementing Container Image Promotion Pipelines- 40mBest Practices In Implementing Container Image Promotion Pipelines
15mKeynote: Best Practices In Implementing 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
57mKiller Docker Workflows for Development
42mBest Practices in Docker Continuous Delivery