Making Docker Actually Work
summary
Containers are useful but immature: expect to redo work when a standard (OCI) lands and avoid using containers for big sites unless switching quickly is possible. Use docker-compose (fig) to define applications, keep compose files and Dockerfiles in git, and put images on GitHub not via ad hoc docker commit. Run a front-end reverse proxy routing container so many apps share one host port. Demo builds and deploys work quickly, but Docker’s default networking lets one container reach another (eg exposed Redis), so treat built‑in networking as insecure.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:17A warning
- 1:01Prologue
- 4:05Turd Bento
- 4:35How Docker Should Work
- 9:51Reverse proxy
- 19:40Final note about security
related talks
45mFumbling Forward - Docker Don'ts
13mBuilding reproducible dev environments with Docker
30mSimplify All the Things with Docker Compose
29mWhy You Should Care About Docker
44mDocker and the Path to a Better Staging Environment
23m12 Factor Frontend Apps through Dockerization
33mDocker Container Lifecycles – Problem or Opportunity?
01h 09mDocker in Production