Best Practices In Implementing Container Image Promotion Pipelines
summary
Concrete claim: promote artifacts, don't rebuild them; practical tools: JFrog Container Registry/Artifactory, JFrog CLI, nginx URL rewrite for virtual hosts; surprising operational fact: Docker Hub throttling and mutable tags force local caching and remote proxy caches Docker Hub; reproducibility tactic: use checksums and build once and promote immutable images across separate registries per maturity; convenience tactic: double tagging links latest to immutable digest so promotion is metadata-only (no network copy) and pipelines can enforce strict quality gates.
AI-written summary · about
chapters (14)
- 0:00Start
- 3:09SHOWNOTES
- 4:44PIPELINE: QUALITY GATES AND VISIBILITY
- 5:55$docker build
- 6:27LET'S docker build IN EVERY ENV!
- 11:21WHAT'S UP WITH THE GATES?!
- 12:10OPTION 1: METADATA TAGS
- 13:02OPTION 2: DOCKER REPOSITORIES
- 14:10SEPARATE REGISTRIES PER ENVIRONMENT
- 16:23VIRTUAL HOSTS/PORTS TO THE RESCUE
- 17:43LET'S ABUSE THINGS!
- 23:29WIN-WIN-WIN
- 27:15STATIC TAGGING VS DYNAMIC TAGGING
- 32:03CONCLUSIONS
related talks
40mBest Practices In Implementing Container Image Promotion Pipelines
15mKeynote: Best 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
42mBest Practices in Docker Continuous Delivery
27mA Million Ways To Promote Changes Between Environments
