The answer is yes in both cases.
- Docker has an internal networking setup. You can create a “network” and all containers in that network communicate with each other, but not with other containers in other networks.
- You can configure your VPN container to expose some ports that it uses to communicate, and then the “regular applications” can make use of those ports to connect through the VPN.
JoeCoT@fedia.io 5 months ago
I don't know of a good way to route other application's traffic through the VPN container with them being in docker containers, unless you use some intermediary setup. That's why I have socks proxies routed through the VPN, so I can selectively put traffic through it. If the app supports a socks proxy you could do it that way. At the least you could use Proxychains to do so if the program does TCP networking.