But it doesn&#x27;t really, it is just another tool to learn like your configuration management software.  Honestly, learning Docker to a high level was WAY easier than getting my Chef knowledge to a mediocre level.  Further, it has other benefits like being MUCH easier to set up well isolated dev environments with Docker than with Chef.  Since we switched we can usually have someone running the dev environment and tests within an hour or so of unboxing their laptop.  With chef running the whole thing from scratch took that long by itself (after you installed all the software) and usually failed.  And the idea that it is too complicated for something simple- I built a sample blogging app that you can deploy to a digital ocean or ec2 machine with like 3 or 4 commands (<a href="https:&#x2F;&#x2F;github.com&#x2F;pbecotte&#x2F;devblog" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;pbecotte&#x2F;devblog</a>).  The system we have built at work has 8 separate services between a bunch of data stores, background workers, and a couple different pieces of our app- but Docker allows you to run the entire environment on your local machine and then deploy that same setup to our cluster, without any differences to account for making all those apps run on one VM for your local environment (which can get bad when one service requires a different version of a ruby gem than another for example).