docker-openvpn-client VS containers

I was planning to do that. I am using this image https://github.com/wfg/docker-openvpn-client

What I want to know is which alternative client can be used to establish a connection to VPNs B and C? I've looked at OpenConnect but it seems that the download links for Windows builds are broken? What about others like SoftEther, OpenVPN or freelan? There's also the possibility of running a containerized Linux client inside Docker, as shown here? I do have WSL (running Debian, solely) and Docker Desktop installed on the machine so maybe? There are more options for native Linux clients (AFAIK) but I'm stuck with Windows 10 and that's not going to change anytime soon.

Because all the traffic is routed into the vpn. You have to provide a route to your local network. I dont know if this is possible with your image. I use this one https://github.com/wfg/docker-openvpn-client there you can set your network via the SUBNETS environment variable.

I'm assuming you followed the instructions at https://github.com/wfg/docker-openvpn-client/pkgs/container/openvpn-client to get the containers set up.

I have a similar setup with rtorrent and wireguard for torrenting: https://gitlab.com/cocainefarm/containers/rtorrent

You need to have an wireguard kernel support on the host ofc, but else you only need wireguard-tools in the container and can use a wg-quick config like usual.

Also with podman or k8s you don't even need it integrated into one container, as all containers in a pod share the same network namespace, so you can have one container running your workload and another one running the VPN.