3 ms·
The problem with docker is that it's Yet Another Tool you have to learn how to install, configure and use. Once you grok what it's doing, how to install it, how
by ajsharp 11y ago
The problem with docker is that it's Yet Another Tool you have to learn how to install, configure and use. Once you grok what it's doing, how to install it, how to run it on OS X, etc, it's powerful, but being forced to learn a new tool to install another, is a bit of a yak shave, and quite frustrating.
- wpietri 11y agoYeah, from the point of view of a 70s university department minicomputer, Docker is another tool. A rapidly evolving one, one that has focused on developer adoption over other concerns. If you're using it to install just one thing on a server where you've installed many other things the old way, it's a pain. When it gets interesting is when you invert the relationship, where you have multiple apps in Docker. Then the main server starts to look quite simple and bare, much easier to maintain. And then things like ECS start to make sense: https://aws.amazon.com/ecs/ https://aws.amazon.com/ecs/ At that point, the OS becomes irrelevant except as a host for containers.
- tgaqw 11y agoThe os should already be an irrelevant host for processes, if developers stopped with this dynamic linking and spreading files and configuration all over the os, instead of a simple contained directory with all it's dependencies and configuration except for the kernel. Like we did in the good old DOS days.