Say's who? To my knowledge, nobody has attempted to build a container platform using the docker spec. For all anyone knows, there's large gaping logic holes needing to be filled. It's simply untested and unproven.
> and already deployed at large scale, via Docker's implementation.
I think you mean to say "Docker is deployed", because again, nobody has tried to implement the docker spec as-of yet.
The docker team spent so long actively avoiding introducing any sort of standardized container specification out of fear someone would come along and eat docker's lunch, that it's hard to believe miraculously overnight you were able to develop a rock-solid specification that clearly addresses all scenarios and is extensible for any 3rd party to implement cleanly.
The docker spec technically has zero implementations, since it was only created (overnight) as an afterthought after your "implementation" was already completed. If anything, the docker spec is an (untested) implementation of docker.
As-of today, the App Container Specification has 3 times more implementations than the docker spec, has far greater adoption, has been refined more significantly over multiple iterations, and has accepted far more community input into it's development.
Let's be genuine here shykes. Your purpose in this thread is to get people talking about docker and cast some shade on the CoreOS team. The very thing you got so upset about when they first announced Rocket and the App Container Specification.