Fumbling Forward - Docker Don'ts
summary
Shows an actual Flask app pipeline built with Docker, Dockerfile layers and caching, Docker Compose linking a web container to Redis, and Docker Machine spawning EC2 hosts — all wired to a CircleCI workflow that repeatedly rebuilds or caches images. Demonstrates pitfalls: Docker commit vs Dockerfile build, ordering lines to avoid reinstalling deps, leftover volumes eating disk, Compose’s build cache and extends mismatch with AWS JSON conversion. Result: a working MVP for deploys, but CircleCI and persistent-data handling remain unresolved.
AI-written summary · about
chapters (12)
- 0:00Introduction and goals
- 1:56Defining continuous delivery
- 4:29Docker fundamentals
- 7:09Working with containers
- 11:02Building with Dockerfiles
- 15:25Docker machine setup
- 16:52Docker compose basics
- 21:27Advanced container linking
- 26:42Optimizing workflows
- 32:07Managing volumes and data
- 34:56Deployment strategies
- 38:44CI integration and questions
related talks
21mMaking Docker Actually Work
38mFrom Docker'fail to Dockerfile.. a true story!
53mDocker Dos And Do Nots
01h 00mDocker for development
23m12 Factor Frontend Apps through Dockerization
28mDocker-Composing Your Way to a Better Development Environment
30mSimplify All the Things with Docker Compose
43mDocker 101: Meet the portable future (tutorial)