Docker and Cloud Foundry: The 3 Use Cases
summary
Three concrete patterns: run apps as Docker images on Diego so CF push a Docker image pulls from a registry, stages, scales, heals and allows SSH into garden-runC containers; deliver services as containers using a Docker service broker with Docker Swarm deployed as a BOSH release so service plans map to container images that publish credentials; and run pipeline steps as containers where Concourse tasks are Docker images, pipelines push images to the registry and can be intercepted. Demos build roughly 10–20 containers; registry, storage and staging performance matter.
AI-written summary · about
chapters (6)
- 0:00Introduction and use cases
- 2:00Running apps as containers
- 9:28Services as containers
- 18:51Pipeline tasks as containers
- 26:52Architectural considerations
- 30:40Q&A session
related talks
43mHow Platforms Work
01h 29mThinking Outside the Container: Running Standalone Apps on Cloud Foundry
48mCloud Foundry - your PaaS on OpenStack
30mPanel Discussion: Buildpacks and Containers for Cloud Foundry
28mDelivering Heterogeneous Architectures
01h 02mCloudFoundry or Kubernetes/Kubo: Choosing the Right Platform for the Job
24mThe Platform Wars, Begun They Have
32mCloud Foundry Diego Update