My problem with Docker is not the abstractions - you need to learn to live with them as they're not going anywhere. I would [probably] be willing to make the [r

My problem with Docker is not the abstractions - you need to learn to live with them as they're not going anywhere. I would [probably] be willing to make the [required] security trade offs and maybe even the complexities and workarounds. My biggest problem is still the amount of noise despite project being alive for over 2 years now. Therefore what you said in: > "the Docker model seems to have absorbed all the hacks without documenting any of the best practices," resonates a lot with me. From the community point of view the ecosystem, despite having some really smart people involved, is swarming with vendors. This is probably good for Docker as a technology company which must be striving to be omnipresent/ubiquitous, but can be [and often is] detrimental for the end users: developers and operators. Saying that Docker is still young, writing good software of Docker scale is tough and takes time, especially given the circumstances I've mentioned above. So let's see where Docker leadership will drive the project.