I’d basically like to run some containers within a VPN and some outside of it. The containers running within the VPN should not be able to send or receive any traffic from outside the VPN (except localhost maybe).
The container could be docker, podman, or even a qemu VM or some other solution if need be.
Is that possible? Dunno if this is the right place to ask.
—Resolution-------
Use https://github.com/qdm12/gluetun folks.
Gluetun, is overkill if you already have a working setup. Your system is able to handle this in a much simple way with built in tools.
You can use
systemdto restrict some daemon to your your VPN IP. For instance here’s an example of doing that with transmission: override of the default unit by using the following command:Then type what you need to override:
[Service] IPAddressDeny=any IPAddressAllow=10.0.0.1 # --> your VPN IP hereAnother option, might be to restrict it to a single network interface:
[Service] RestrictNetworkInterfaces=wg0 # --> your VPN interfaceSave the file and run
systemctl daemon-reloadfollowed bysystemctl restart transmission-daemon.serviceand it should be applied.This is a simple and effective solution that doesn’t require more stuff.
Thanks, great to know! systemd can really do a lot.
Anti Commercial-AI license