Containerization War Stories
summary
Pinterest migrates a quarter of infrastructure to Docker over about a year, moving from brittle masterful Puppet to container images and a sidecar model. Key wins: immutable builds catch errors at build time and provision time drops from 30→5 minutes. Surprising failures: Docker’s default overlay network adds ~20% latency so teams use host networking; the default json log driver blocks and freezes apps; cron + overlayfs hardlinks break scheduled jobs. Operational fixes: --live-restore, --init, and per-container init processes, plus gradual automation for dependency discovery.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:26Why migrate to containers
- 3:43Challenges with Puppet
- 6:36Benefits of containerization
- 9:51Container architecture
- 12:47Orchestration planning
- 13:45War stories and lessons
- 20:18Automation and outcomes
- 22:19Q&A session
related talks
47mPatterns for Docker Success
26mContainerization crossroads: Experiences-Experiments-Expectations
29mDocker for Managers
24mFrom Zero to a Full Docker Based IT Teams
49mIn Silicon Valley, Engineers Deploy-and-Tell: Stories About Dockerizing an Application
59mBeyond Docker Buzzwords
01h 04mPreparing your Dockerised Application for Production
43mServer Infrastructure for Rails in 2016