3 ms·
There are a great many factual errors in this article and I'm sure someone will write a proper response, but I thought someone should address the most glaring:
by predakanga 11y ago
There are a great many factual errors in this article and I'm sure someone will write a proper response, but I thought someone should address the most glaring:
- The repeated assertion that you can only use one process container is false. As an example, the most popular non-official base image (phusion/baseimage) provides a full system including SSHd and Cron
- No integration points
Docker provides an extensive event stream[0], as do their tools (such as Registry[1])
- "ps, ls, find [...] are useless here"
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
- "You can not easily and directly access your durable non-volatile data storage"
One of the most basic concepts in Docker is that of a "volume"[2]; essentially a directory that bypasses Docker'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.
- No authentication for images
This one's true to a certain extent. While most images aren't currently signed (that's a relatively new feature[4]), it's disingenuous to say that there's no authentication at all. Docker enforces the use of HTTPS to talk to registries, and requires HTTP authentication for registry accounts. It's not signing, but it's something.
Finally, just as it'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's work being done to remove it, but it can't go soon enough in my opinion.
There are a great many reasons you might not want to use Docker, but a lot of what's listed on this site just doesn't check out.
EDIT: Formatting
[0]: https://docs.docker.com/engine/reference/api/docker_remote_api/#docker-events https://docs.docker.com/engine/reference/api/docker_remote_a...
[1]: https://github.com/docker/docker-registry/tree/master/docker_registry/extensions https://github.com/docker/docker-registry/tree/master/docker...
[2]: https://docs.docker.com/engine/userguide/dockervolumes/#data-volumes https://docs.docker.com/engine/userguide/dockervolumes/#data...
[3]: https://docs.docker.com/engine/userguide/dockervolumes/#mount-a-host-directory-as-a-data-volume https://docs.docker.com/engine/userguide/dockervolumes/#moun...
[4]: https://blog.docker.com/2015/08/content-trust-docker-1-8/ https://blog.docker.com/2015/08/content-trust-docker-1-8/