Ask HN: What is the actual purpose of Docker?
For me, it is the ultimate in the idea in Continuous Delivery of "build once." I can be very confident that the docker image I build in the first stage of my pipeline will operate correctly in production. This is because that identical image was used for unit tests, to integration and functional testing, to the staging environment and finally production. There is no difference than configuration.<p>This is the core that Docker solves, and in such a way that developers can do most of  the dependency wrangling for me. I don't even mind Java anymore because the CLASSPATHs can be figured out once, documented in the Dockerfile in a repeatable programatic fashion, and then ignored.<p>In my opinion the rest of it is gravy. Nice tasty gravy, but I don't care so much about the rest at the moment.<p><i></i>Edit:<i></i> As danesparz points out, nobody has mentioned immutable architecture. This is what we do at Clarify.io. See also: <a href="https://news.ycombinator.com/item?id=9845255" rel="nofollow">https://news.ycombinator.com/item?id=9845255</a>