Those of you who know me from $WORK know (oh, you know) that I’m currently heavily involved in testing out Docker for use here, and that I’ve fully drunk not only the Kool-Aid, but also any other Docker-related beverage that might be out there.
I’ve presented the Docker concept to a couple of our groups here, evangelized to individual co-workers, spent hours testing, developing, deploying, re-testing, evaluating, etc, etc, all the things about Docker. I’m working on processes, policies, infrastructure and code all related to how Docker can potentially work in our environment.
I literally cannot think of a single thing that my small team – part of the larger Unix team at $WORK, itself a part of the Systems Infrastructure department – …I can’t think of a single thing that my team does that could not be entirely encompassed in Docker containers. I can’t think of anything that we do that wouldn’t be improved, that wouldn’t be automated, that wouldn’t be scaled, that wouldn’t be made better in at least ONE way by moving it to Docker.
I am so on-board with Docker that I literally dreamed about it. I dreamed about presenting Docker to a group of co-workers last night. I, fully asleep in my bed, laid out all the good things about Docker, all the challenges we would face, all the policies and procedures that would change, and all the processes that would be streamlined.
At this point, I woke up and thought perhaps, perhaps, I’d been working a little too much with Docker recently, and maybe I needed to take a break and work on something else.
Naaaaahhhhhhh…it’s too cool! Vive la Docker!
I’m beginning to copy over my technology-related posts from Google+ to this blog, mostly so I have an easy-to-read record of them. This one was originally published on 26 March 2014: A Dream of Docker