Wireguard docker is sleeping after installing of kernel headers about docker-wireguard HOT 22 CLOSED

The readme and your logs are pretty clear on what's going on and what you need to try

from docker-wireguard.

Running:

sudo apt install --reinstall libraspberrypi0 libraspberrypi-{bin,dev,doc} raspberrypi-bootloader raspberrypi-kernel

installed the stable kernel files.

Running the following compose file:

version: "2"
services:
wireguard:
image: linuxserver/wireguard
container_name: wireguard
ports:
- 51969:51820/udp
cap_add:
- NET_ADMIN
- SYS_MODULE
volumes:
- /opt/docker/wireguard/config:/config
- /lib/modules:/lib/modules
- /etc/resolv.conf:/etc/resolv.conf:ro
environment:
PUID: 1000
PGID: 1000
TZ: Europe/Berlin
SERVERURL: -------------.myfritz.net
SERVERPORT: 51969
PEERS: 2
PEERDNS: 192.168.178.1
restart: unless-stopped

This config works finally fine for me. I had to tell the docker that my DNS is my fritzbox because it behaves strange when the DNS is on the same host.
Thanks a lot for your support!

from docker-wireguard.

See my heavily downvoted post above yours. Please read the docs. We put a lot of time and effort into them.

from docker-wireguard.

After tried so many things I've made my self easy to follow guide to install wireguard on Rocky Linux (probably on Centos as well)

First Make sure secure boot is disabled on host OS i.e. Rocky Linux / Centos

Step 1: install epel and elrepo

sudo dnf install elrepo-release epel-release -y

Step 1 - optional: fix elrepo mirror issue

if you face any issue running dnf update after installing elrepo then edit /etc/yum.repos.d/elrepo.repo and comment out mirrorlist=http://mirrors.elrepo.org/mirrors-elrepo.el8

sudo vi /etc/yum.repos.d/elrepo.repo
# mirrorlist=http://mirrors.elrepo.org/mirrors-elrepo.el8

Step 2: update

sudo dnf update -y

Step 3: install wireguard and enable it

sudo dnf install kmod-wireguard wireguard-tools -y
sudo dnf copr enable jdoss/wireguard
sudo dnf update -v
sudo dnf install wireguard-dkms -y
sudo modprobe wireguard

Step 4: reboot the server

reboot

Now you should be able to run wireguard on Rocky Linux / Centos with your docker-compose.yaml file
if not then you can compare it with mine or use it as it is

version: "3"
services:
 wireguard:
   image: linuxserver/wireguard
   container_name: wireguard
   cap_add:
     - NET_ADMIN
     - SYS_MODULE
   environment:
     - PUID=1000
     - PGID=1000
     - TZ=Asia/Karachi
     - SERVERURL=wireguard.mydomain.com # Replace it with public facing url
     - SERVERPORT=51820 #optional
     - PEERS=2 #optional
     - PEERDNS=auto #optional
     - INTERNAL_SUBNET=10.13.13.0 #optional
   volumes:
     - ./config:/config
     - /usr/src:/usr/src
     - /lib/modules:/lib/modules
   ports:
     - 51820:51820/udp
   sysctls:
     - net.ipv4.conf.all.src_valid_mark=1
   restart: unless-stopped

from docker-wireguard.

I have read the above Posts But I am not sure about the solution and what could be a cause for my issue Kindly provide a suggestion for my issue.

This part of the readme covers all the different scenarios:
https://github.com/linuxserver/docker-wireguard#application-setup

from docker-wireguard.

I have read the above Posts But I am not sure about the solution and what could be a cause for my issue Kindly provide a suggestion for my issue.

I've also created a repo for it, if posted guide doesn't work for you then you may open issue there and I'll look into it
https://github.com/uzairali001/docker-wireguard-rhel

from docker-wireguard.

Thanks for your suggestion above steps resolve my issue But I am not sure about the - SERVERURL=wireguard.mydomain.com # Replace it with public-facing URL can I remove this or should I add it to yaml file ?

According to the official documentation you can remove this so container can determine the url itself but I recommend you to explicitly set it to public facing url or IP which your client will be used to connect to

from docker-wireguard.

Thanks @uzairali001 -- very clear and helpful. For anyone using CentOS 7 or below, this also worked too based on @uzairali001 steps:

  yum install yum-plugin-copr
  yum copr enable jdoss/wireguard
  yum install wireguard-dkms -y
  modprobe wireguard
  docker restart wireguard

from docker-wireguard.

Thanks for opening your first issue here! Be sure to follow the issue template!

from docker-wireguard.

You need to map /lib/modules:/lib/modules as described in the readme

from docker-wireguard.

Thanks for the tip.
Totally overseen that. :/ But the behaviour is still the same with this yaml:

version: "2"
services:
wireguard:
image: linuxserver/wireguard
container_name: wireguard
ports:
- 51969:51969/udp
cap_add:
- NET_ADMIN
- SYS_MODULE
volumes:
- /opt/docker/wireguard/config:/config
- /lib/modules:/lib/modules
- /usr/src:/usr/src
- /etc/resolv.conf:/etc/resolv.conf:ro
environment:
PUID: "1000"
PGID: "1000"
TZ: "Europe/Berlin"
SERVERURL: "....net"
SERVERPORT: "51969"
PEERS: "2"
PEERDNS: "192.168.178.54"
restart: unless-stopped

from docker-wireguard.

Please read the readme more carefully.
You are doing several things wrong.
Don't map resolv.conf
Don't change the internal port, it needs to be 51820
Remove the quotes around env vars
Post a full log

from docker-wireguard.

Hi aptalca,

To be on the safe side I use the yaml from the Readme:

version: "2.1"
services:
wireguard:
image: linuxserver/wireguard
container_name: wireguard
cap_add:
- NET_ADMIN
- SYS_MODULE
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/London
- SERVERURL=....
- SERVERPORT=51820
- PEERS=1 #optional
- PEERDNS=auto #optional
volumes:
- /opt/docker/wireguard/config:/config
- /lib/modules:/lib/modules
ports:
- 51820:51820/udp

The log is still the same: :/

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.,
[s6-init] ensuring user provided files have correct perms...exited 0.,
[fix-attrs.d] applying ownership & permissions fixes...,
[fix-attrs.d] done.,
[cont-init.d] executing container initialization scripts...,
[cont-init.d] 01-envfile: executing... ,
[cont-init.d] 01-envfile: exited 0.,
[cont-init.d] 10-adduser: executing... ,
,
-------------------------------------,
_ (),
| | ___ _ _,
| | / | | | / \ ,
| | _ \ | | | () |,
|| |/ || _/,
,
,
Brought to you by linuxserver.io,
-------------------------------------,
,
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: 1000,
-------------------------------------,
,
[cont-init.d] 10-adduser: exited 0.,
[cont-init.d] 30-config: executing... ,
Uname info: Linux 8f5f1b9ea5a7 5.4.58-v7l+ #1335 SMP Thu Aug 13 22:23:01 BST 2020 armv7l armv7l armv7l GNU/Linux,
Error: Unknown device type.,
**** The wireguard module is not active, will attempt kernel header install and module compilation. ****,
**** Attempting kernel header install ****,
Get:1 http://ports.ubuntu.com/ubuntu-ports bionic InRelease [242 kB],
Get:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB],
Get:3 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease [74.6 kB],
Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease [88.7 kB],
Get:5 http://ports.ubuntu.com/ubuntu-ports bionic/universe armhf Packages [11.0 MB],
Get:6 http://ports.ubuntu.com/ubuntu-ports bionic/main armhf Packages [1,277 kB],
Get:7 http://ports.ubuntu.com/ubuntu-ports bionic/restricted armhf Packages [12.5 kB],
Get:8 http://ports.ubuntu.com/ubuntu-ports bionic/multiverse armhf Packages [157 kB],
Get:9 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf Packages [1,177 kB],
Get:10 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main armhf Packages [843 kB],
Get:11 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted armhf Packages [11.0 kB],
Get:12 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse armhf Packages [4,825 B],
Get:13 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main armhf Packages [8,247 B],
Get:14 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe armhf Packages [8,101 B],
Get:15 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted armhf Packages [5,504 B],
Get:16 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe armhf Packages [706 kB],
Get:17 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse armhf Packages [1,849 B],
Get:18 http://ports.ubuntu.com/ubuntu-ports bionic-security/main armhf Packages [578 kB],
Fetched 16.2 MB in 9s (1,720 kB/s),
Reading package lists...,
**** Raspbian kernel naming convention detected, attempting to install raspbian kernel headers ****,
Warning: apt-key output should not be parsed (stdout is not a terminal),
OK,
Hit:1 http://ports.ubuntu.com/ubuntu-ports bionic InRelease,
Hit:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease,
Get:3 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB],
Hit:4 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease,
Hit:5 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease,
Get:6 http://archive.raspberrypi.org/debian buster/main Sources [93.7 kB],
Get:7 http://archive.raspberrypi.org/debian buster/main armhf Packages [331 kB],
Fetched 457 kB in 7s (65.9 kB/s),
Reading package lists...,
Reading package lists...,
Building dependency tree...,
Reading state information...,
The following NEW packages will be installed:,
raspberrypi-kernel-headers,
0 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.,
Need to get 26.2 MB of archives.,
After this operation, 171 MB of additional disk space will be used.,
Get:1 http://archive.raspberrypi.org/debian buster/main armhf raspberrypi-kernel-headers armhf 1.20200811-1 [26.2 MB],
Fetched 26.2 MB in 8s (3,455 kB/s),
Selecting previously unselected package raspberrypi-kernel-headers.
,
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 13991 files and directories currently installed.)
,
Preparing to unpack .../raspberrypi-kernel-headers_1.20200811-1_armhf.deb ...
,
Unpacking raspberrypi-kernel-headers (1.20200811-1) ...
,
Setting up raspberrypi-kernel-headers (1.20200811-1) ...
,
run-parts: executing /etc/kernel/header_postinst.d/dkms 5.4.51+
,

• dkms: running auto installation service for kernel 5.4.51+
  [ OK ]
  ,
  run-parts: executing /etc/kernel/header_postinst.d/dkms 5.4.51-v7+
  ,
• dkms: running auto installation service for kernel 5.4.51-v7+
  [ OK ]
  ,
  run-parts: executing /etc/kernel/header_postinst.d/dkms 5.4.51-v7l+
  ,
• dkms: running auto installation service for kernel 5.4.51-v7l+
  [ OK ]
  ,
  run-parts: executing /etc/kernel/header_postinst.d/dkms 5.4.51-v8+
  ,
• dkms: running auto installation service for kernel 5.4.51-v8+
  [ OK ]
  ,
  **** Kernel headers don't seem to be available, can't compile the module. Sleeping now. . . ****,

from docker-wireguard.

You're using a beta kernel, but the headers package inside the container provide headers for a different kernel: 5.4.58 vs 5.4.51

Go back to installing the correct headers on host and mapping /usr/src:/usr/src

from docker-wireguard.

I am having the same issue. The above fix didn't work for me unfortunately.

Here is how I am running the container: docker run -d --name=wireguard --cap-add=NET_ADMIN --cap-add=SYS_MODULE -e PUID=1000 -e PGID=1000 -e TZ=Europe/Berlin -e SERVERURL=<my-server-url> -e SERVERPORT=51820 -e PEERS=1 -e PEERDNS=8.8.8.8 -e INTERNAL_SUBNET=10.13.13.0 -p 51820:51820/udp -v /path/to/my/volume/folder/config:/config -v /lib/modules:/lib/modules --sysctl="net.ipv4.conf.all.src_valid_mark=1" --restart unless-stopped ghcr.io/linuxserver/wireguard:latest

and here is the log output from the container

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing... 
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing... 

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \ 
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/


Brought to you by linuxserver.io
-------------------------------------

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:    1000
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing... 
Uname info: Linux 260ee9e1c154 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 2019 armv7l armv7l armv7l GNU/Linux
RTNETLINK answers: Operation not supported
**** The wireguard module is not active, will attempt kernel header install and module compilation. ****
**** Attempting kernel header install ****
Get:1 http://ports.ubuntu.com/ubuntu-ports bionic InRelease [242 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease [74.6 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease [88.7 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports bionic/multiverse armhf Packages [157 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports bionic/main armhf Packages [1,277 kB]
Get:7 http://ports.ubuntu.com/ubuntu-ports bionic/restricted armhf Packages [12.5 kB]
Get:8 http://ports.ubuntu.com/ubuntu-ports bionic/universe armhf Packages [11.0 MB]
Get:9 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main armhf Packages [1,371 kB]
Get:10 http://ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse armhf Packages [6,814 B]
Get:11 http://ports.ubuntu.com/ubuntu-ports bionic-updates/restricted armhf Packages [15.6 kB]
Get:12 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe armhf Packages [1,788 kB]
Get:13 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main armhf Packages [11.2 kB]
Get:14 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe armhf Packages [11.0 kB]
Get:15 http://ports.ubuntu.com/ubuntu-ports bionic-security/restricted armhf Packages [8,755 B]
Get:16 http://ports.ubuntu.com/ubuntu-ports bionic-security/main armhf Packages [998 kB]
Get:17 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe armhf Packages [1,112 kB]
Get:18 http://ports.ubuntu.com/ubuntu-ports bionic-security/multiverse armhf Packages [2,809 B]
Fetched 18.2 MB in 13s (1,396 kB/s)
Reading package lists...
**** Raspbian kernel naming convention detected, attempting to install raspbian kernel headers ****
Warning: apt-key output should not be parsed (stdout is not a terminal)
OK
Hit:1 http://ports.ubuntu.com/ubuntu-ports bionic InRelease
Get:2 http://archive.raspberrypi.org/debian buster InRelease [32.9 kB]
Hit:3 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease
Hit:4 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease
Hit:5 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease
Get:6 http://archive.raspberrypi.org/debian buster/main Sources [106 kB]
Get:7 http://archive.raspberrypi.org/debian buster/main armhf Packages [372 kB]
Fetched 511 kB in 5s (99.0 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  raspberrypi-kernel-headers
0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
Need to get 27.6 MB of archives.
After this operation, 180 MB of additional disk space will be used.
Get:1 http://archive.raspberrypi.org/debian buster/main armhf raspberrypi-kernel-headers armhf 1.20210303-1 [27.6 MB]
Fetched 27.6 MB in 1min 24s (331 kB/s)
Selecting previously unselected package raspberrypi-kernel-headers.
(Reading database ... 14037 files and directories currently installed.)
Preparing to unpack .../raspberrypi-kernel-headers_1.20210303-1_armhf.deb ...
Unpacking raspberrypi-kernel-headers (1.20210303-1) ...
Setting up raspberrypi-kernel-headers (1.20210303-1) ...
run-parts: executing /etc/kernel/header_postinst.d/dkms 5.10.17+
 * dkms: running auto installation service for kernel 5.10.17+           [ OK ] 
run-parts: executing /etc/kernel/header_postinst.d/dkms 5.10.17-v7+
 * dkms: running auto installation service for kernel 5.10.17-v7+        [ OK ] 
run-parts: executing /etc/kernel/header_postinst.d/dkms 5.10.17-v7l+
 * dkms: running auto installation service for kernel 5.10.17-v7l+       [ OK ] 
run-parts: executing /etc/kernel/header_postinst.d/dkms 5.10.17-v8+
 * dkms: running auto installation service for kernel 5.10.17-v8+        [ OK ] 
**** Kernel headers don't seem to be available, can't compile the module. Sleeping now. . . ****

from docker-wireguard.

What is your host os?

Assuming raspbian, you need to be on buster and need to have the latest kernel, which is 5.10.17. But your host is on kernel 4.14.98, which means you're either not on buster, or you haven't updated in a long time.

from docker-wireguard.

What is your host os?

$ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

you haven't updated in a long time

no, I have not. Thanks for the info, I will update my distro and try again 👌🏼

from docker-wireguard.

Also having the same issue, could it be that Rocky Linux is not supported yet?

version: "2.1"
services:
  wireguard:
    image: ghcr.io/linuxserver/wireguard
    container_name: wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=1000
      - PGID=1000
     - TZ=Europe/London
      - SERVERURL=wireguard.mydomain.com #optional
      - SERVERPORT=51820 #optional
      - PEERS=1 #optional
      - PEERDNS=auto #optional
      - INTERNAL_SUBNET=10.13.13.0 #optional
      - ALLOWEDIPS=0.0.0.0/0 #optional
    volumes:
      - ./config:/config
      - /lib/modules:/lib/modules
    ports:
      - 51820:51820/udp
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    restart: unless-stopped

$ cat /etc/os-release
NAME="Rocky Linux"
VERSION="8.4 (Green Obsidian)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.4"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Rocky Linux 8.4 (Green Obsidian)"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:rocky:rocky:8.4:GA"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
ROCKY_SUPPORT_PRODUCT="Rocky Linux"
ROCKY_SUPPORT_PRODUCT_VERSION="8"

wireguard    | Uname info: Linux 1919482b44f3 4.18.0-305.19.1.el8_4.x86_64 #1 SMP Wed Sep 15 19:12:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
wireguard    | Error: Unknown device type.
wireguard    | **** The wireguard module is not active, will attempt kernel header install and module compilation. ****
wireguard    | **** Attempting kernel header install ****
wireguard    | Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
wireguard    | Hit:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
wireguard    | Hit:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease
wireguard    | Reading package lists...
wireguard    | **** No kernel headers found in the Ubuntu or Debian repos!! Will try the headers from host (if mapped), may or may not work ****
wireguard    | **** Kernel headers don't seem to be available, can't compile the module. Sleeping now. . . ****

from docker-wireguard.

The above fix didn't work for me as well Kindly suggest on this

[root@localhost wireguard]# docker logs 67826b132baa
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 01-migrations: executing...
[migrations] started
[migrations] no migrations found
[cont-init.d] 01-migrations: exited 0.
[cont-init.d] 02-tamper-check: executing...
[cont-init.d] 02-tamper-check: exited 0.
[cont-init.d] 10-adduser: executing...

      _         ()
     | |  ___   _    __
     | | / __| | |  /  \
     | | \__ \ | | | () |
     |_| |___/ |_|  \__/

Brought to you by linuxserver.io

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: 1000

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-module: executing...
Uname info: Linux 67826b132baa 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
RTNETLINK answers: Operation not supported
**** The wireguard module is not active, will attempt kernel header install and module compilation. ****
**** Attempting kernel header install ****
Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic/universe Sources [11.5 MB]
Get:5 http://archive.ubuntu.com/ubuntu bionic/main Sources [1,063 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic/restricted Sources [5,823 B]
Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse Sources [216 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1,344 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 MB]
Get:11 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [13.5 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources [18.2 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [598 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/restricted Sources [30.2 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [655 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [2,256 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [3,067 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [29.0 kB]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [863 kB]
Get:20 http://archive.ubuntu.com/ubuntu bionic-security/universe Sources [365 kB]
Get:21 http://archive.ubuntu.com/ubuntu bionic-security/restricted Sources [26.8 kB]
Get:22 http://archive.ubuntu.com/ubuntu bionic-security/main Sources [331 kB]
Get:23 http://archive.ubuntu.com/ubuntu bionic-security/multiverse Sources [8,784 B]
Get:24 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages [2,628 kB]
Get:25 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [1,478 kB]
Get:26 http://archive.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [21.1 kB]
Get:27 http://archive.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [829 kB]
Fetched 39.3 MB in 1min 53s (349 kB/s)
Reading package lists...
**** No kernel headers found in the Ubuntu or Debian repos!! Will try the headers from host (if mapped), may or may not work ****
**** Kernel headers don't seem to be available, can't compile the module. Sleeping now. . . ****
[root@localhost wireguard]# cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

[root@localhost wireguard]#

version: "2.1"
services:
wireguard:
image: lscr.io/linuxserver/wireguard
container_name: wireguard
cap_add:
- NET_ADMIN
- SYS_MODULE
environment:
- PUID=1000
- PGID=1000
- TZ=Asia/Kolkata
- SERVERURL=wg.aidan.to #optional
- SERVERPORT=51820 #optional
- PEERS=1 #optional
- PEERDNS=auto #optional
- INTERNAL_SUBNET=10.13.13.0 #optional
- ALLOWEDIPS=0.0.0.0/0 #optional
volumes:
- ./config:/config
- /lib/modules:/lib/modules
ports:
- 51820:51820/udp
sysctls:
- net.ipv4.conf.all.src_valid_mark=1
restart: unless-stopped
~

from docker-wireguard.

I have read the above Posts But I am not sure about the solution and what could be a cause for my issue Kindly provide a suggestion for my issue.

from docker-wireguard.

Thanks for your suggestion above steps resolve my issue But I am not sure about the - SERVERURL=wireguard.mydomain.com # Replace it with public-facing URL can I remove this or should I add it to yaml file ?

from docker-wireguard.

#57 (comment)

i have same problem. i use this workaround, and wg in CentOS 8 its working now. thank you.

from docker-wireguard.