From: logcabin@fastmail.net
To: wireguard@lists.zx2c4.com
Subject: Re: WireGuard on Docker
Date: Sat, 21 Jul 2018 17:47:58 -0400 [thread overview]
Message-ID: <1532209678.585688.1448515984.39AF7871@webmail.messagingengine.com> (raw)
In-Reply-To: <CAPDu8706B0ZHjqCk6rUfdD0DNC1Z1ADS6_z7Kc+60p3P26tSHQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2422 bytes --]
I'm wondering if the kernel module is loaded:
# modinfo wireguard
On Tue, Jul 10, 2018, at 4:16 AM, Mohammad Amir Heshmatkhah wrote:
> Hi,
> I want to run WireGuard on a docker container as server,
> I try difrent base Images but I get this error message every time:
>
> [#] ip link add wg0 type wireguard
> RTNETLINK answers: Operation not supported
> Unable to access interface: Protocol not supported
> [#] ip link delete dev wg0
> Cannot find device "wg0"
>
> Here is 3 Dokerfiles I tried:
>
> FROM alpine:3.7
> RUN apk upgrade --update \
> && echo http://dl-cdn.alpinelinux.org/alpine/edge/testing >>
> /etc/apk/repositories \> && apk add --no-cache bash wireguard-tools
>
> ENTRYPOINT [ "wg-quick", "up", "wg0" ]
>
> ————————————-
>
> FROM ubuntu:16.04
> RUN apt-get update && apt-get install -y software-properties-common
> apt-utils \> && add-apt-repository ppa:wireguard/wireguard \
> && apt-get update \
> && apt-get install -y iproute linux-headers-$(uname -r) wireguard-dkms
> wireguard-tools wireguard>
> ENTRYPOINT [ "wg-quick", "up", "wg0" ]
>
> ————————————-
>
> FROM debian:9
> RUN echo "deb http://deb.debian.org/debian/ unstable main" >
> /etc/apt/sources.list.d/unstable.list \> && printf 'Package: *\nPin: release a=unstable\nPin-Priority: 150\n' >
> /etc/apt/preferences.d/limit-unstable \> && apt-get update && apt-get install -y wireguard
>
> ENTRYPOINT [ "wg-quick", "up", "wg0" ]
>
> ————————————-
>
> I run this containers with:
>
> sudo docker run -it -v $(pwd)/config:/etc/wireguard/ -v /dev:/dev
> -v /lib/modules:/lib/modules --cap-add=ALL --privileged <image
> name here>>
> where wg0.conf is located in " $(pwd)/config/wg0.conf" on host machine>
> ————————————-
>
> and here is my wg0.conf file:
>
> [Interface]
> Address = 172.26.10.1/24
> SaveConfig = true
> PrivateKey = <server private key here>
> ListenPort = 40540
>
> [Peer]
> PublicKey = <client public key here>
> AllowedIPs = 172.26.10.2/32
>
> ————————————-
>
> So, How can I fix this "*Unable to access interface: Protocol not
> supported*" error?> _________________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
[-- Attachment #2: Type: text/html, Size: 9862 bytes --]
next prev parent reply other threads:[~2018-07-21 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 8:16 WireGuard on Docker Mohammad Amir Heshmatkhah
2018-07-21 21:47 ` logcabin [this message]
[not found] ` <CAJqFBzwF-3jvB9yNqcQdcn9qp_i2xPua1fjeVoY7a-j0es=VYw@mail.gmail.com>
2018-07-22 6:44 ` Zsolt Hegyi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1532209678.585688.1448515984.39AF7871@webmail.messagingengine.com \
--to=logcabin@fastmail.net \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).