[dasil003]

Docker isn’t supposed to make development faster, it’s supposed to give a standard way to package code and dependencies so that a small infra team can support a much larger dev team developing a large number of services with heterogeneous language and library versions.

[finaliteration]

Exactly this. I’m the DevOps lead at my current company and my life would be hell if I had to manage not only remote machines but also local dev machines and all the package versions, dependencies, etc, that can differ. Docker adds some overhead and some headaches, sure, but once we got our CI/CD pipeline running with Docker life got about ten times easier because we weren’t spending hours in a Slack channel trying to chase down a package that someone forgot to upgrade or compiled with the wrong modules.

[timrichard]

I agree too. I kicked off an application server project for a business unit in a large company using Docker. Aside from the core image of my application server, I used docker-compose to orchestrate nginx and Redis instances to support it. That setup remains available to a small team of developers. From the first production release and to date, corp DevOps build the core app server image in their pipeline, and deploy it with a different load balancer and a compatible key value store. It worked in that configuration the first time, and there's never been an issue.

The flexibility and modularity is a big plus to me.

[akvadrako]

I disagree. The main reason Docker is superior to packer and other VM-based systems is speed. Less time waiting for builds, less time starting your servers (including during development), less time setting up a dev environment, ...