Docker & Buildpacks: One App, Two Options for Deploying to Cloud Foundry
summary
Deploys the same Go HTTP app two ways: buildpack produces a runnable droplet via the stager and Diego staging task after a CF push no-start then CF start, while Docker requires docker build, push to a registry and Cloud Foundry creating a docker droplet (metadata) that Diego pulls and runs. The talk shows which steps run where, how garden runs container images, how CVE patches differ (operator vs developer action), and tradeoffs for local iteration and security.
AI-written summary · about
chapters (12)
- 0:00Introduction to speakers
- 1:06Buildpacks vs Docker
- 2:10Sample application overview
- 2:44Deploying with buildpacks
- 6:18Creating a Dockerfile
- 8:31Deploying Docker to CF
- 10:41Garden container engine
- 11:25Security vulnerabilities
- 13:54Local development strategies
- 17:37Porting between providers
- 18:57Pros and cons summary
- 20:40Q&A and conclusion
