Wireguard isn't creating Peer Folders

After my wireguard stopped working I decided to dump the whole thing and start over. I deleted the container and stack using portainer then reloaded everything. The second time around instead of creating the peer1 and peer2 folders it is creating the following two empty folders.

custom-cont-init.d and custom-services.d

Here is the stack I'm using. It worked just fine the first time around.

version: "2.1"
services:
  wireguard:
    image: lscr.io/linuxserver/wireguard
    container_name: wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=1000                     #See point 1.
      - PGID=100                      #See point 1.
      - TZ=America/New_York           #Should be adjusted according to your location
      - SERVERURL=My IP              #See point 2.
      - SERVERPORT=51820              #To change see next post
      - PEERS=2                       #See point 2. Number of clients you want to configure
      - PEERDNS=auto
      - INTERNAL_SUBNET=10.13.13.0    #Only change if it conflicts
      - ALLOWEDIPS=0.0.0.0/0
    volumes:
      - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config:/config           #See point 1.
      - /lib/modules:/lib/modules
    ports:
      - 51823:51820/udp               #To change see next post
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    restart: unless-stopped

Yes, I'm using Docker-Config for each of my containers(Nextcloud, Bitwarden and Wireguard). Here is what is in Docker-Config:

drwxr-sr-x  4 pi   users 4096 Mar 13  2021 Bitwarden_Self_Host
drwxr-sr-x  2 pi   users 4096 Feb 25 15:34 bitwarden
drwxrwsr-x  7 pi   users 4096 Feb 13  2021 cache
drwxr-sr-x  2 pi   users 4096 Feb 12 01:16 coredns
drwxr-sr-x  2 root root  4096 Mar  4 16:26 custom-cont-init.d (File created by wireguard instead of Peer1 and 2)
drwxr-sr-x  2 root root  4096 Mar  4 16:26 custom-services.d  (File created by wireguard instead of Peer1 and 2)
drwxrwsr-x  9 pi   users 4096 Feb 13  2021 nextcloud
drwxrwsr-x  4 pi   users 4096 Feb 13  2021 nextclouddb
drwxr-sr-x  2 pi   users 4096 Feb 12 01:16 server
drwxrwsr-x 12 pi   users 4096 Feb 13  2021 swag
drwxr-sr-x  2 pi   users 4096 Feb 12 01:16 templates
-rw-------  1 pi   users  585 Feb 12 01:16 wg0.conf

Zitat

To support the app dev(s) visit:

WireGuard: https://www.wireguard.com/donations/

To support LSIO projects visit:

https://www.linuxserver.io/donate/

-------------------------------------

GID/UID

-------------------------------------

User uid: 1000

User gid: 100

-------------------------------------

[cont-init.d] 10-adduser: exited 0.

[cont-init.d] 30-module: executing...

Uname info: Linux 2be563ae216e 5.10.63-v7+ #1496 SMP Wed Dec 1 15:58:11 GMT 2021 armv7l armv7l armv7l GNU/Linux

**** It seems the wireguard module is already active. Skipping kernel header install and module compilation. ****

[cont-init.d] 30-module: exited 0.

[cont-init.d] 40-confs: executing...

**** Server mode is selected ****

**** External server address is set to 24.128.146.227 ****

**** External server port is set to 51820. Make sure that port is properly forwarded to port 51820 inside this container ****

**** Internal subnet is set to 10.13.13.0 ****

**** AllowedIPs for peers 0.0.0.0/0 ****

**** PEERDNS var is either not set or is set to "auto", setting peer DNS to 10.13.13.1 to use wireguard docker host's DNS. ****

**** Server mode is selected ****

**** No changes to parameters. Existing configs are used. ****

[cont-init.d] 40-confs: exited 0.

[cont-init.d] 90-custom-folders: executing...

[cont-init.d] 90-custom-folders: exited 0.

[cont-init.d] 99-custom-scripts: executing...

[custom-init] no custom files found exiting...

[cont-init.d] 99-custom-scripts: exited 0.

[cont-init.d] done.

[services.d] starting services

[services.d] done.

[#] ip link add wg0 type wireguard

[#] wg setconf wg0 /dev/fd/63

[#] ip -4 address add 10.13.13.1 dev wg0

.:53

CoreDNS-1.8.7

linux/arm, go1.17.6, a9adfd5

[#] ip link set mtu 1420 up dev wg0

[#] ip -4 route add 10.13.13.3/32 dev wg0

[#] ip -4 route add 10.13.13.2/32 dev wg0

[#] iptables -A FORWARD -i wg0 -j ACCEPT; iptables -A FORWARD -o wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

Alles anzeigen

Port forwarding is correct. There was no change from when it was working.

Zitat von Zoki

volumes: - /srv/dev-disk-by-uuid-1c0dc0b4-d37c-4a43-b9ed-597a8dd4f64f/Docker-Config/wireguard:/config #See point 1.

I deleted everything and redeployed the container as suggested above and the peer1 and 2 files were created, so everything is working again.