by polvi on 2/8/16, 6:48 PM with 19 comments
by NetStrikeForce on 2/8/16, 10:38 PM
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?
Disclosure: I am behind https://wormhole.network 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 https://github.com/pjperez/docker-wormhole - it doesn't require changes on the host itself, but can't be orchestrated.
by shykes on 2/8/16, 10:13 PM
[1] https://blog.docker.com/2015/11/docker-multi-host-networking...
by politician on 2/8/16, 11:06 PM
by danfitch on 2/8/16, 9:00 PM
by chrissnell on 2/8/16, 10:28 PM
by vetrom on 2/9/16, 12:49 AM
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.
by emeraldd on 2/8/16, 8:38 PM