Killer Docker Workflows for Development
summary
Argues Docker works best as a development tool when workflows are specific: build images as immutable artifacts, push them to a registry, and deploy the same image through dev, QA and prod; use the same image from dev to production and separate build → release → run steps. Enforces concrete rules: one process per container, commit Dockerfiles and composer.lock, use --no-cache and --pull for builds, and ship logs to fluentd or a central store.
AI-written summary · about
chapters (35)
- 0:00Intro
- 0:33What Is Docker?
- 3:11Normal Bare-Metal Server
- 4:35Virtual Machines
- 6:57Containers are just walled processes
- 8:04Docker is an Ecosystem
- 8:39How does it work?
- 17:22Codebase
- 18:25Repo Tips
- 20:06Monoliths vs Micro Services
- 22:16Dependencies
- 24:47Configuration
- 26:14Use Environment Vars
- 27:12Backing Services
- 27:23Everything is "external"
- 29:30Build, release, run
- 29:41The Workflow
- 32:50Build Step-Start Small
- 33:33docker build
- 35:31Sample usage
- 39:54Port Binding
- 41:07Concurrency
- 41:23How well does your app handle scaling?
- 43:14Disposability
- 45:23Dev/prod Parity
- 46:56Logging in Docker
- 48:05Push logs remotely
- 48:49Setting up fluentd
- 50:00Setting up ElasticSearch and Kibana
- 50:28Viewing Logs
- 50:55Logging notes
- 51:26Admin Processes
- 51:45Containerizing Your Commands
- 53:11Set up docker-compose
- 55:47When doing a deployment
related talks
01h 00mDocker for development
49mContinuous Delivery at Docker age
16mBest Practices for Container Image Promotion Pipelines
33mDocker Container Lifecycles – Problem or Opportunity?
44mFast Track to Docker for Developers
45mHigh‑performance Development Workflow with Kubernetes
41mDocker Container Lifecycles, problem or opportunity?
36mDockerization in the land of Ruby