we should take a moment to think about the motives of a commercial for-profit company such as Docker, before we embed it into everything. Shykes seems to take i

we should take a moment to think about the motives of a commercial for-profit company such as Docker, before we embed it into everything. Shykes seems to take issue with me pointing these things out, as I would expect him to. What about the motives of CoreOS, also a for profit company? I'd argue that a single, universal standardized container format specification is crucial for such a piece of technology that will soon be (is?) at the heart of all application deployments, both servers and desktops. Correct me if I'm wrong, but doesn't the new container proposal do the exact opposite of this? Why not collaborate with Docker on a container format? From the Github post: But here's a suggestion for you. If you were to complain that Docker's image format and runtime specification, as massively adopted as it is, is not appropriately documented, and it could be made easier to produce alternate implementations - then I would completely agree with you. You state that Docker has absolutely zero intention of collaborating openly on a standardized container format however they explicitly invite help into standardizing and documenting theirs, which is currently the most commonly used. This is the last thing I'm going to leave here. http://xkcd.com/927/ http://xkcd.com/927/ It may not be the most credible of sources, however it makes the point I am trying to make quite well. Making an additional standard when there is already something well established does nothing but fragment the ecosystem. You may be questioning the motives of Docker, Inc, however that leaves the rest of us to question the motives of CoreOS. I did not seen ANY efforts at collaboration by CoreOS before they released their own container format/runtime. Especially in the passive-agressive (mostly agressive) way in which they did it. If their motives were truely to create a "single, universal standardized container format specification", the first step would have been to at least attempt to work with Docker to create this. Instead of this happening, this whole argument has turned into a pissing match between the two companies. Seriously, both companies need to set aside their differences and have a real discussion about this, not just doing things on the internet to piss each other off.