<story><title>Docker 1.12: Now with Built-In Orchestration</title><url>https://blog.docker.com/2016/06/docker-1-12-built-in-orchestration/</url></story><parent_chain></parent_chain><comment><author>d33</author><text>I chose Docker for my project with hope that it would help me create an easily reproducible development environment... And I&amp;#x27;m not really sure if it was a good idea. There&amp;#x27;s so many moving parts and I can&amp;#x27;t name one that actually works well. Configuring storage is a hell (running out of disk space can lead to errors that are really difficult to debug), the dance with bridges makes configuring firewall a terrible experience. I definitely wouldn&amp;#x27;t recommend it as a stable container solution.</text></comment>
<story><title>Docker 1.12: Now with Built-In Orchestration</title><url>https://blog.docker.com/2016/06/docker-1-12-built-in-orchestration/</url></story><parent_chain></parent_chain><comment><author>csears</author><text>Just based on the details mentioned in the keynote, the services API and swarm features look very similar to what&amp;#x27;s offered by Kubernetes... service discovery, rolling updates, load balancing, health checks, auto-healing, advanced scheduling.&lt;p&gt;I guess this was to be expected, but it&amp;#x27;s also kind of sad. I think it would have been a more strategic move to embrace Kubernetes instead of trying to compete with it.</text></comment>