thrnz

I don't think it's possible to use a dedicated IP with this container atm. I'd probably consider adding support once its added to their own [standalone scripts](https://github.com/pia-foss/manual-connections/issues/84), though as it's...

I've not had much experience using macvlan networks with Docker I'm afraid, so nothing immediately jumps out as being wrong. I'll have a poke around if I get the time...

I'd be surprised if it was an issue. [```wg-quick```](https://git.zx2c4.com/wireguard-tools/about/src/man/wg-quick.8) is used to setup wireguard, which should set the wireguard interace as the default gateway for all outgoing traffic. Because wireguard...

I run a short script in a bare-bones 'helper' container to keep an eye on ```port.dat``` and do what it needs to when it changes. It might be a bit...

`sudo` shouldn't be needed for the container to work. It might be worth opening an issue to see if anyone else has a similar problem first. I'd be reluctant to...

https://github.com/thrnz/docker-wireguard-pia/blob/1a5d1410f792435c27a9c9ec63fab94dc063d24a/run#L180 I imagine you'd get that error if ```PORT_PERSIST``` is set to something unexpected. The Dockerfile sets it to 0 by default, and the script expects it to be either...

That compose file will be setting ```PORT_PERSIST``` to an empty value. The script expects it to be a number, so is throwing an error when it encounters it. I haven't...

I think that's a Docker thing, where when the original container goes down, it's entire network stack also goes down so other containers that may have been sharing its network...

Thanks for this. Port forwarding and adding access to the LAN isn't strictly needed to access services running on the vpn container's network stack. It might be preferable to use...

That error can happen when ports are set on the other container rather than the vpn's container. It's a bit counter intuitive, but the other container essentially inherits the vpn...