Wireguard in Docker

[Apocalyptic Wabbit 0]

Is there a way to use wireguard's CLI tools to build a wireguard configuration file for TorGuard? I'd like to build a docker container that connects to Wireguard servers, but I want to script out the configuration file instead of having TorGuard generate it for me.... Is this possible?

[uNc 4]

On 10/7/2019 at 3:31 PM, Apocalyptic Wabbit said:

Is there a way to use wireguard's CLI tools to build a wireguard configuration file for TorGuard? I'd like to build a docker container that connects to Wireguard servers, but I want to script out the configuration file instead of having TorGuard generate it for me.... Is this possible?

 A Docker container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.

Whats this have to do with anything?

[Apocalyptic Wabbit 0]

You misunderstood. Typically there is a docker entry script which sets up container functionality. Most wireguard examples uses a scripted key exchange to configure wg and sending the peer ip to the server. TorGuard seems to favor pre-generating configs. This won't work in docker as ip's are assigned on container start. So I can't use a static config... 

I've moved on to using a raspi privoxy wireguard device. I would still be interested in this thread to understand how to make TorGuards service work with docker. 

[doh 0]

On 10/15/2019 at 2:13 AM, Apocalyptic Wabbit said:

You misunderstood. Typically there is a docker entry script which sets up container functionality. Most wireguard examples uses a scripted key exchange to configure wg and sending the peer ip to the server. TorGuard seems to favor pre-generating configs. This won't work in docker as ip's are assigned on container start. So I can't use a static config... 

I've moved on to using a raspi privoxy wireguard device. I would still be interested in this thread to understand how to make TorGuards service work with docker. 

 

I agree, this is a complete pain! Restarting my container can mean having to re-generate a new Wireguard config file to get new public/private keys - not really sustainable...