add buster backports

README.md

@@ -177,7 +177,7 @@ If the environment variable `PEERS` is set to a number, the container will run i
 
 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 add more peers/clients later on, you increment the `PEERS` environment variable and recreate the container.
 
 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).
 
@@ -257,6 +257,7 @@ Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64
 
 ## Versions
 
+* **26.04.20:** - Add Buster backports repo for Debian.
 * **20.04.20:** - Fix typo in client mode conf existence check.
 * **13.04.20:** - Fix bug that forced conf recreation on every start.
 * **08.04.20:** - Add arm32/64 builds and enable multi-arch (rpi4 with ubuntu and raspbian buster tested). Add CoreDNS for `PEERDNS=auto` setting. Update the `add-peer`/`show-peer` scripts to utilize the templates and the `INTERNAL_SUBNET` var (previously missed, oops).

readme-vars.yml

@@ -67,7 +67,7 @@ app_setup_block: |
   
   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 add more peers/clients later on, you increment the `PEERS` environment variable and recreate the container.
   
   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).
 
@@ -78,6 +78,7 @@ app_setup_block: |
 
 # changelog
 changelogs:
+  - { date: "26.04.20:", desc: "Add Buster backports repo for Debian." }
   - { date: "20.04.20:", desc: "Fix typo in client mode conf existence check." }
   - { date: "13.04.20:", desc: "Fix bug that forced conf recreation on every start." }
   - { date: "08.04.20:", desc: "Add arm32/64 builds and enable multi-arch (rpi4 with ubuntu and raspbian buster tested). Add CoreDNS for `PEERDNS=auto` setting. Update the `add-peer`/`show-peer` scripts to utilize the templates and the `INTERNAL_SUBNET` var (previously missed, oops)." }

root/etc/cont-init.d/30-config

@@ -38,7 +38,7 @@ elif uname -v | grep -q 'Debian'; then
   echo "Debian host detected, attempting to install kernel headers from Debian Buster repo"
   curl -s https://ftp-master.debian.org/keys/archive-key-10.asc | apt-key add -
   echo -e \
-    "deb http://deb.debian.org/debian buster main contrib non-free\ndeb-src http://deb.debian.org/debian buster main contrib non-free" \
+    "deb http://deb.debian.org/debian buster main contrib non-free\ndeb-src http://deb.debian.org/debian buster main contrib non-free\ndeb http://deb.debian.org/debian buster-backports main contrib non-free\ndeb-src deb http://deb.debian.org/debian buster-backports main contrib non-free" \
     > /etc/apt/sources.list.d/debian.list
   apt-get update
   if apt-cache show linux-headers-$(uname -r) 2&>1 >/dev/null; then