I've got a strong interest on overlay networking solutions like Weave, but I'm not an expert on Docker and other container solutions.<p>What's the new thing here? If I understood correctly, it seems that you can connect your Docker host to an overlay network, so your containers can access other containers and resources through it. Am I correct to think this facilitates orchestration of the containers' network?<p>Disclosure: I am behind <a href="https://wormhole.network" rel="nofollow">https://wormhole.network</a> which could be seen as some sort of Weave competitor, but it's not. It covers other use cases, even though there's some overlapping e.g. overlay multi-host networking for containers <a href="https://github.com/pjperez/docker-wormhole" rel="nofollow">https://github.com/pjperez/docker-wormhole</a> - it doesn't require changes on the host itself, but can't be orchestrated.
I haven't looked at this in detail, but does this work with the standard networking features introduced in Docker 1.9 [1] and 1.10 [2]? Can I still use 'docker network create/connect' and the DNS service discovery features of Docker? Can containers interoperate regardless of the choice of Docker plugin, or will they only work on a plugin based on the weave proxy? The wording in the post leaves that ambiguous.<p>[1] <a href="https://blog.docker.com/2015/11/docker-multi-host-networking-ga/" rel="nofollow">https://blog.docker.com/2015/11/docker-multi-host-networking...</a><p>[2] <a href="https://blog.docker.com/2016/02/docker-1-10/" rel="nofollow">https://blog.docker.com/2016/02/docker-1-10/</a>
Video that goes into detail about what Calico. <a href="https://www.youtube.com/watch?list=PLlh6TqkU8kg_Eydfk1Nyt6iK7wM8v9bRA&v=-8qrULl-zkk" rel="nofollow">https://www.youtube.com/watch?list=PLlh6TqkU8kg_Eydfk1Nyt6iK...</a>
Other than IPv6 support, is there a reason to use Calico/Weave over Flannel? We've been very happy with Flannel, especially using the clean CoreOS-Flannel integration.
I'm looking forward to setting up some trial deployments of calico at my workplace.<p>While there is an ease of understanding of bridged and/or overlayed networks, native end-to-end routing between containers with regular IP datagrams and container-level addressability has been on my wishlist for a long time.