Downloaded 41 times
Uploaded byDocker, Inc.
Docker Container Lifecycles, Problem or Opportunity? by Baruch Sadogursky, JFrog
The document discusses the lifecycle of Docker containers and the integration of JFrog Artifactory with Docker. It addresses challenges related to version control, repository management, and the importance of quality gates in builds. The content emphasizes minimizing repository interactions and enhancing security measures for managing Docker images and binaries.
More Related Content
Similar to Docker Container Lifecycles, Problem or Opportunity? by Baruch Sadogursky, JFrog
Docker Container Lifecycles, Problem or Opportunity? by Baruch Sadogursky, JFrog
- 1. Docker Container Lifecycles- Problem or Opportunity? Baruch Sadogursky Dev Advocate @JFrog
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8. Poll Time! Heard aboutDocker Can do the tutorial PoCing, playing etc. Production, baby!
- 12. JFrog Artifactory +Docker
- 13. Who’s using Dockerand nothing else?
- 14. The Promotion Pyramid Developmentbuilds Dev Integration tests Integr. tests Staging Pre-Prod Prod Amount of builds Build/Deploytime Amount of binaries
- 15. Pipeline: Quality Gatesand Visibility Source: Agile ALM, Michael Hüttermann, Manning Publications Co.
- 17.
- 19.
- 21.
- 22.
- 23. Let’s fix it(again)!
- 24. Let’s fix it(again)!
- 25. What you codeis (not) what you get
- 27. The stronger thequality gates, more trust you have.
- 29.
- 30.
- 31. The Anatomy ofDocker Tag
- 32. Wait a second,how can I have more than one repository per host now?!
- 33. How can wesupport this? https://host:8081/artifactory/docker-dev/busybox https://host:8081/artifactory/docker-staging/busybox https://host:8081/artifactory/docker-qa/busybox https://host:8081/artifactory/docker-prod/busybox
- 34.
- 35. Virtual hosts/ports tothe rescue https://host:8081/artifactory/docker-dev/busybox docker tag host:port/busybox Context name Virtual repository name Tag name
- 36. server { listen 5001; server_name192.168.99.100; if ($http_x_forwarded_proto = '') { set $http_x_forwarded_proto $scheme; } rewrite ^/(v1|v2)/(.*) /artifactory/api/docker/docker-dev/$1/$2; … } }
- 38. But then yourealize… Wait a second, now I need to pull, retag and push for every step?!
- 40.
- 41.
- 42. What we did? -Minimize number of repositories docker interact with
- 43. What we did? -Minimize number of repositories docker interact with - deploy to virtual (backed by dev repository)
- 44. What we did? -Minimize number of repositories docker interact with - deploy to virtual (backed by dev repository) - promote within artifactory
- 45. What we did? -Minimize number of repositories docker interact with - deploy to virtual (backed by dev repository) - promote within artifactory - Resolve from virtual (production-ready images)
- 46.
- 47. Finding the needlein haystack of binaries
- 48. Finding the needlein haystack of binaries - What deployed where - Tracing binaries to sources
- 49. Finding the needlein haystack of binaries - What deployed where - Tracing binaries to sources - Cherry pick the one to prod
- 50.
- 52.
- 53.
- 54.
- 55. r/w on repolevel is not enough
- 56. r/w on repolevel is not enough - read, write, delete, annotate - on any level – registry, repo, image or tag
- 57. Content Control –Don’t Lose It
- 60.
Editor's Notes
- #14 Solomon Hykes