[NetStrikeForce]

I've got a strong interest on overlay networking solutions like Weave, but I'm not an expert on Docker and other container solutions.

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.

[vishvananda]

I haven't come across your project before. Any relation to my (similarly named) project https://github.com/vishvananda/wormhole ? I always thought that one of the most interesting piece of my project was easy ipsec tunnel setup. It turns out that setting ip ipsec tunnels is pretty tricky.

[NetStrikeForce]

Holy cr*p! haha! first time I see your project, too.

I think both are a bit different. My project is based on SoftEther and using an external server as a pivotal point, so all the members of the network only need outbound 443/TCP access. It's not point to point unfortunately. The idea is to make sure it works on as many scenarios as possible.

I'm just adding all the server management and simplification layer, but both server and clients are 100% SoftEther.

[justincormack]

No, Docker already supports overlay networks, including Weave a default one that ships with it, and Calico.