|
|
|
|
|
by derefr
3677 days ago
|
|
Question for anyone who knows: say I've got a few VMs in a private network (on e.g. DigitalOcean), and want to connect them to a corporate Intranet. If I've got a Docker container sitting on a public bridge interface of one of those VMs, running a VPN daemon, is that container separated enough from its host to be effectively used as the VPN gateway for the rest of the network the VMs are on—including the VM hosting the container? Or do I really need a separate VM to serve that function? I ask because, in the case where I've only got one VM to bridge into a corporate Intranet, I always want to set that VM up with a network-to-network VPN (instead of just making it a VPN client) in case its network grows from one node to several. But adding a whole extra VPN gateway instance just to serve a "network" of one machine is a pretty high overhead for a small project. |
|
https://www.zerotier.com
You can run this inside Docker containers with a few extra capabilities (allow tap, allow ioctls) which is probably similar to what you need for other in-container solutions. You can also run it on intranet servers, desktops, phones, etc., and connect everything to a common virtual backplane.
Edit: you can also bridge this to docker0 since it supports Ethernet bridging and run it on a Docker host. We're working on better/cleaner Docker integration but it's all do-able now. Just takes a bit of sysadmin know-how.