████ ████ ████
██ ████ ██
██ ████████ ██
██ ████████ ██
██ ████████ ██
██ ████████ ██
██ ████████ ██
██ ████ ██
████ ████ ████
- @tianon on GitHub
- @tianon on Twitter
tianon
on several popular IRC networks4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
- Happily Married, Father of Two
- SVP of Operations @ InfoSiftr BOOTH 648 at Interop!
- Docker Core Maintainer
- OCI Runtime Spec TDC member
- Debian Developer, uploading
When preparing an application to run inside a Docker container (so called "Dockerization"), there are a few potential baby dragons waiting to strike on the unsuspecting developer (or the poor ops they hand the application off to). In this talk, we'll explore a few of these snags, and the mitigation strategies that have been the most effective in our experiences working with Dockerizing software.