Submitted via IRC for TheMightyBuzzard
Docker is a great tool. But Docker containers are not a cure-all. If you really want to understand how Docker is impacting the channel, you have to understand its limitations.
Docker containers have become massively popular over the past several years because they start faster, scale more easily and consume fewer resources than virtual machines.
But that doesn't mean that Docker containers are the perfect solution for every type of workload. Here are examples of things Docker can't do or can't do well:
- Run applications as fast as a bare-metal server.
- Provide cross-platform compatibility.
- Run applications with graphical interfaces.
- Solve all your security problems.
I kinda miss just running services directly on physical servers. Guess I'm getting old.
Source: http://thevarguy.com/open-source/when-not-use-docker-understanding-limitations-containers
(Score: 1, Interesting) by Anonymous Coward on Saturday August 26 2017, @04:04PM
In all seriousness, I have been wondering if this is really the motivation behind containers. Costs have been cut so much that they are not really allowed to buy dedicated servers anymore. However, the sysadmins and devs got used to the features that VMs provided and nested virtualization has been unstable and slow until recently on hardware with support. Therefore, the market for "VMs" that could run on VMs sprang up and containers of various types were born.