Using Docker-in-Docker for your CI or testing environment? Think twice.

1 · Jérôme Petazzoni · Sept. 3, 2015, midnight
The primary purpose of Docker-in-Docker was to help with the development of Docker itself. Many people use it to run CI (e.g. with Jenkins), which seems fine at first, but they run into many “interesting” problems that can be avoided by bind-mounting the Docker socket into your Jenkins container instead. Let’s see what this means. If you want the short solution without the details, just scroll to the bottom of this article. ☺ Docker-in-Docker: the good More than two years ago, I contributed the ...