@ -122,10 +124,11 @@ Container images are configured using parameters passed at runtime (such as thos
| `-e PUID=1000` | for UserID - see below for explanation |
| `-e PGID=1000` | for GroupID - see below for explanation |
| `-e TZ=Europe/London` | Specify a timezone to use EG Europe/London |
| `-e SERVERURL=wireguard.domain.com` | External IP or domain name for docker host. Required for server mode. |
| `-e SERVERPORT=51820` | External port for docker host. Required for server mode. |
| `-e SERVERURL=wireguard.domain.com` | External IP or domain name for docker host. Used in server mode. If set to `auto`, the container will try to determine and set the external IP automatically |
| `-e SERVERPORT=51820` | External port for docker host. Used in server mode. |
| `-e PEERS=1` | Number of peers to create confs for. Required for server mode. |
| `-e PEERDNS=8.8.8.8` | DNS server set in peer/client configs. |
| `-e PEERDNS=8.8.8.8` | DNS server set in peer/client configs. Used in server mode. |
| `-e INTERNAL_SUBNET=10.13.13.0` | Internal subnet for the wireguard and server and peers (only change if it clashes). Used in server mode. |
| `-v /config` | Contains all relevant configuration files. |
@ -166,16 +169,18 @@ If you're on a debian/ubuntu based host with a custom or downstream distro provi
This can be run as a server or a client, based on the parameters used.
## Server Mode
Pass the environment variables `SERVERURL`, `SERVERPORT`, `PEERS` and `PEERDNS`, and the container will generate all necessary confs for both the server and the clients. The client config qr codes will be output in the docker log. They will also be saved in text and png format under `/config/peerX`.
If the environment variable `PEERS` is set to a number, the container will run in server mode and the necessary server and peer/client confs will be generated. The peer/client config qr codes will be output in the docker log. They will also be saved in text and png format under `/config/peerX`.
If there is an existing `/config/wg0.conf`, the above environment variables won't have any affect. To add more peers/clients later on, you can run `docker exec -it wireguard /app/add-peer` while the container is running.
Variables `SERVERURL`, `SERVERPORT`, `INTERNAL_SUBNET` and `PEERDNS` are optional variables used for server mode. Any changes to these environment variables will trigger regeneration of server and peer confs. Peer/client confs will be recreated with existing private/public keys. Delete the peer folders for the keys to be recreated along with the confs.
To add more peers/clients later on, you can run `docker exec -it wireguard /app/add-peer` while the container is running.
To display the QR codes of active peers again, you can use the following command and list the peer numbers as arguments: `docker exec -it wireguard /app/show-peer 1 4 5` (Keep in mind that the QR codes are also stored as PNGs in the config folder).
To recreate all server and client confs, set the above env vars, delete `/config/wg0.conf` and restart the container. Client confs will be recreated with existing private/public keys. Delete the peer folders for the keys to be recreated along with the confs.
The templates used for server and peer confs are saved under `/config/templates`. Advanced users can modify these templates and force conf generation by deleting `/config/wg0.conf` and restarting the container.
## Client Mode
Drop your client conf into the config folder as `/config/wg0.conf` and start the container.
Do not set the `PEERS` environment variable. Drop your client conf into the config folder as `/config/wg0.conf` and start the container.
@ -243,5 +248,6 @@ Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64
## Versions
* **05.04.20:** - Add `INTERNAL_SUBNET` variable to prevent subnet clashes. Add templates for server and peer confs.
* **01.04.20:** - Add `show-peer` script and include info on host installed headers.
- {env_var:"SERVERURL", env_value:"wireguard.domain.com", desc:"External IP or domain name for docker host. Required for server mode."}
- {env_var:"SERVERPORT", env_value:"51820", desc:"External port for docker host. Required for server mode."}
- {env_var:"SERVERURL", env_value:"wireguard.domain.com", desc:"External IP or domain name for docker host. Used in server mode. If set to `auto`, the container will try to determine and set the external IP automatically"}
- {env_var:"SERVERPORT", env_value:"51820", desc:"External port for docker host. Used in server mode."}
- {env_var:"PEERS", env_value:"1", desc:"Number of peers to create confs for. Required for server mode."}
- {env_var:"PEERDNS", env_value:"8.8.8.8", desc:"DNS server set in peer/client configs."}
- {env_var:"PEERDNS", env_value:"8.8.8.8", desc:"DNS server set in peer/client configs. Used in server mode."}
- {env_var:"INTERNAL_SUBNET", env_value:"10.13.13.0", desc:"Internal subnet for the wireguard and server and peers (only change if it clashes). Used in server mode."}
optional_block_1:false
optional_block_1_items:""
@ -65,6 +66,7 @@ custom_compose: |
- SERVERPORT=51820#optional
- PEERS=1#optional
- PEERDNS=8.8.8.8#optional
- INTERNAL_SUBNET=10.13.13.0#optional
volumes:
- /path/to/appdata/config:/config
- /lib/modules:/lib/modules
@ -84,18 +86,21 @@ app_setup_block: |
This can be run as a server or a client, based on the parameters used.
## Server Mode
Pass the environment variables `SERVERURL`, `SERVERPORT`, `PEERS` and `PEERDNS`, and the container will generate all necessary confs for both the server and the clients. The client config qr codes will be output in the docker log. They will also be saved in text and png format under `/config/peerX`.
If the environment variable `PEERS` is set to a number, the container will run in server mode and the necessary server and peer/client confs will be generated. The peer/client config qr codes will be output in the docker log. They will also be saved in text and png format under `/config/peerX`.
If there is an existing `/config/wg0.conf`, the above environment variables won't have any affect. To add more peers/clients later on, you can run `docker exec -it wireguard /app/add-peer` while the container is running.
Variables `SERVERURL`, `SERVERPORT`, `INTERNAL_SUBNET` and `PEERDNS` are optional variables used for server mode. Any changes to these environment variables will trigger regeneration of server and peer confs. Peer/client confs will be recreated with existing private/public keys. Delete the peer folders for the keys to be recreated along with the confs.
To add more peers/clients later on, you can run `docker exec -it wireguard /app/add-peer` while the container is running.
To display the QR codes of active peers again, you can use the following command and list the peer numbers as arguments:`docker exec -it wireguard /app/show-peer 1 4 5` (Keep in mind that the QR codes are also stored as PNGs in the config folder).
To recreate all server and client confs, set the above env vars, delete `/config/wg0.conf` and restart the container. Client confs will be recreated with existing private/public keys. Delete the peer folders for the keys to be recreated along with the confs.
The templates used for server and peer confs are saved under `/config/templates`. Advanced users can modify these templates and force conf generation by deleting `/config/wg0.conf` and restarting the container.
## Client Mode
Drop your client conf into the config folder as `/config/wg0.conf` and start the container.
Do not set the `PEERS` environment variable. Drop your client conf into the config folder as `/config/wg0.conf` and start the container.
# changelog
changelogs:
- {date:"05.04.20:", desc:"Add `INTERNAL_SUBNET` variable to prevent subnet clashes. Add templates for server and peer confs."}
- {date:"01.04.20:", desc:"Add `show-peer` script and include info on host installed headers."}
aptalca
4 years ago