Copy them all into your /config folder and make the scripts executable with chmod +x. We'll also need ca. so the container trusts the endpoint, and connect_to_wireguard_with_token.sh which we'll modify a bit later. You might want to make it a bit less "noisy" as you're going to be running it headless but it won't hurt to have that extra information while we're playing around. We can grab the get_region_and_token.sh script and use it more or less as-is.
You need a dummy wg0.conf to get started otherwise the Wireguard container won't get to the point of executing the PIA token/conf scripts. env file (or docker secrets) for our login details. Wireguardįirst up we need a client container that's the easy part version: "2.4" It's still not really designed for the docker use-case, however, so I spent the afternoon playing around to get it working the way I wanted and I thought I'd share in case it helps anyone.
However, as of last week they have published a Github repo with scripts and instructions for rigging things up by hand. IntroductionĬompared to a lot of VPN providers PIA have been pretty slow off the mark in supporting DIY Wireguard connections they've had Wireguard support in their client for a while but that doesn't help if you want to use something like the linuxserver/wireguard container as your client. Also get_region_and_token.sh is now get_token.sh and get_region.sh so you'll need to run the two of them in your init script ( get_token.sh first). Since posting this the scripts have changed slightly so the line numbers are no longer correct, that said the functional elements are still the same so it shouldn't be too hard to figure out where to make the changes.
0 kommentar(er)
