Through all the noise, this comment is exactly what I care about. For a new project, which tech's should I choose? If I were Docker, I would organize the ecosy

Through all the noise, this comment is exactly what I care about. For a new project, which tech's should I choose? If I were Docker, I would organize the ecosystem for the end user on a nice clean website that explicitly lists the specific layers and technology options, some of which are from Docker, and some of which are from third-parties. Yes, they'll give mention to competitors, but at least it creates clarity and puts some meat behind their claims of "Open". At present, I'm thinking of the following: * CONTAINER: Stick w/ Docker since until a competing standard like Rocket is mature, everyone has to support Docker, even CoreOS * CONTAINER MANAGEMENT: Use CoreOS. Per above, they have to support Docker until Rocket is fully baked. Then Rocket and CoreOS will probably have synergies you can't get with Docker / CoreOS. Also, from [1]: These three [Docker] orchestration services are targeted for general availability in Q2, 2015. I honestly don't know what the other layers and decisions are yet. Perspective and clarification is welcome. [1] http://blog.docker.com/2014/12/docker-announces-orchestration-for-multi-container-distributed-apps/ http://blog.docker.com/2014/12/docker-announces-orchestratio...