&gt; we use docker intensively CI in Jenkins for documented, project-specific build environments<p>This.  Doing apt-get install on Travis builds to spin up <i>my</i> required tools on every build was slow and a PITA.  I started using GitLab CI with the Docker executor[0], that&#x27;s reduced to `docker pull myimage` which is often times cached locally.  Build time when from up to 10s of minutes -&gt; seconds.<p>I built a Docker image for building Android AOSP projects[1].  Few people use Docker for build environments where it&#x27;s immensely valuable.  I don&#x27;t want to develop my low level Android platform code on Ubuntu 14.04, I&#x27;d rather throw the build over the wall to a pre-vetted build image that <i>always</i> works.<p>Sure I could roll my own special Jenkins slave to do this, but why not leverage Docker?  Perhaps it&#x27;d be too easy to use the <i>same</i> Docker image on my development laptop.<p>I do agree with the author in some respects that some people don&#x27;t fully understand when containers are valuable and instead containerize all the things!<p>[0] <a href="http:&#x2F;&#x2F;doc.gitlab.com&#x2F;ci&#x2F;docker&#x2F;using_docker_images.html" rel="nofollow">http:&#x2F;&#x2F;doc.gitlab.com&#x2F;ci&#x2F;docker&#x2F;using_docker_images.html</a><p>[1] <a href="https:&#x2F;&#x2F;hub.docker.com&#x2F;r&#x2F;kylemanna&#x2F;aosp&#x2F;" rel="nofollow">https:&#x2F;&#x2F;hub.docker.com&#x2F;r&#x2F;kylemanna&#x2F;aosp&#x2F;</a>