There are a great many factual errors in this article and I&#x27;m sure someone will write a proper response, but I thought someone should address the most glaring:<p>- The repeated assertion that you can only use one process container is false. As an example, the most popular non-official base image (phusion&#x2F;baseimage) provides a full system including SSHd and Cron<p>- No integration points<p>Docker provides an extensive event stream[0], as do their tools (such as Registry[1])<p>- &quot;ps, ls, find [...] are useless here&quot;<p>This depends on your system setup; on a standard Debian setup, all container processes are visible to the actual system. ps, top, netstat, etc will all work just fine<p>- &quot;You can not easily and directly access your durable non-volatile data storage&quot;<p>One of the most basic concepts in Docker is that of a &quot;volume&quot;[2]; essentially a directory that bypasses Docker&#x27;s abstraction layers, for performance and durability. Additionally, using your normal storage is absolutely trivial[3] - if Linux can see it, you can use it.<p>- No authentication for images<p>This one&#x27;s true to a certain extent. While most images aren&#x27;t currently signed (that&#x27;s a relatively new feature[4]), it&#x27;s disingenuous to say that there&#x27;s no authentication at all. Docker enforces the use of HTTPS to talk to registries, and requires HTTP authentication for registry accounts. It&#x27;s not signing, but it&#x27;s something.<p>Finally, just as it&#x27;s a personal bugbear of mine, I would note that the userland proxy is a very real problem. It causes major issues if you need wide port ranges, spawning an instance of the proxy per port per container. There&#x27;s work being done to remove it, but it can&#x27;t go soon enough in my opinion.<p>There are a great many reasons you might not want to use Docker, but a lot of what&#x27;s listed on this site just doesn&#x27;t check out.<p>EDIT: Formatting<p>[0]: <a href="https:&#x2F;&#x2F;docs.docker.com&#x2F;engine&#x2F;reference&#x2F;api&#x2F;docker_remote_api&#x2F;#docker-events" rel="nofollow">https:&#x2F;&#x2F;docs.docker.com&#x2F;engine&#x2F;reference&#x2F;api&#x2F;docker_remote_a...</a><p>[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker-registry&#x2F;tree&#x2F;master&#x2F;docker_registry&#x2F;extensions" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;docker&#x2F;docker-registry&#x2F;tree&#x2F;master&#x2F;docker...</a><p>[2]: <a href="https:&#x2F;&#x2F;docs.docker.com&#x2F;engine&#x2F;userguide&#x2F;dockervolumes&#x2F;#data-volumes" rel="nofollow">https:&#x2F;&#x2F;docs.docker.com&#x2F;engine&#x2F;userguide&#x2F;dockervolumes&#x2F;#data...</a><p>[3]: <a href="https:&#x2F;&#x2F;docs.docker.com&#x2F;engine&#x2F;userguide&#x2F;dockervolumes&#x2F;#mount-a-host-directory-as-a-data-volume" rel="nofollow">https:&#x2F;&#x2F;docs.docker.com&#x2F;engine&#x2F;userguide&#x2F;dockervolumes&#x2F;#moun...</a><p>[4]: <a href="https:&#x2F;&#x2F;blog.docker.com&#x2F;2015&#x2F;08&#x2F;content-trust-docker-1-8&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.docker.com&#x2F;2015&#x2F;08&#x2F;content-trust-docker-1-8&#x2F;</a>