We solve all of those use cases in our cluster management system of which Docker is a key enabling component, except for point 5, though we do have other components that require multiple steps to provision. I bet we could run Hadoop if we needed it.<p>It&#x27;s easy to point at Docker and say it&#x27;s a trivial wrapper around some technologies that have been around for years and call everyone crazy for buying into the &#x27;Docker is going to change the (sysadmin) world&#x27; hype. Of course in essence it&#x27;s pretty trivial, many things are.<p>Docker, and Docker-like systems really are changing the sysadmin world. Easily formalised software environments is what this hype is about, and the fact that the Docker community isn&#x27;t really looking at the stateful service problem right, doesn&#x27;t mean they&#x27;re not enabled by Docker either.<p>To me, and to many &#x27;devops&#x27; (i.e. developers rolling into sysadmin roles) Docker was eye-opening. We reduced our chef scripts by 80%, and thus our headaches by 95%. It&#x27;s saving us months of ops work. If you were a seasoned sysadmin and rolling your eyes at the fact that we were rolling out application level services in the same chef codebase we were setting up our system environments with, then yeah you already were better than us. But as far as I could tell the way we used to do it really was the status quo, at least in the startup&#x2F;small it business world.