Let Diego Manage Your Docker Application
summary
Diego adds a local cache: during staging it pulls a Docker Hub image, stores it in a private docker registry, and subsequent scale/start uses the cached copy so instances stay consistent and start faster. Diego runs images with its garden backend (not the Docker daemon). Private images require credentials only at staging (then discarded). Integration is opt‑in via diego docker cache and the demo succeeds; feature is MVP/experimental with followups planned for HTTPS, S3 storage and HA.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:46What is Diego
- 2:29Diego perceives two worlds
- 2:54Diego overview
- 4:33Docker integration
- 6:48Community projects
- 10:18Problems with Diego
- 13:23Private Docker Registry
- 15:58Demo
- 19:00Future
- 20:28Summary
related talks
33mDocker and Cloud Foundry: The 3 Use Cases
32mCloud Foundry Diego Update
36mClosing the Developer Experience Gap of your Container Platforms
10mCost Optimization in Cloud Foundry Through Economies of Scale
29mNavigating the Cloud Foundry Ecosystem of Ecosystems: An ISV Perspective
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
23mEmbracing Cloud-Native Mindset For Organizational Success
42mRunning your private IoT Cloud Stack