From: Kirill K <kovalev.kirill.a@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Docker Swarm over WireGuard
Date: Sun, 18 Nov 2018 06:45:57 +0300 [thread overview]
Message-ID: <CAAWPTbOG8=XEwB-rCs9i2JYuMoJM-J_5RR4U2S_W4F+4katc_g@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1281 bytes --]
Hello there!
I'm using WireGuard about a year and really happy with it. It's
easy-to-use, fast and stable. Great thanks for this precious software.
Sometimes I use servers from providers which do not have any internal
network. So I tried to setup Docker Swarm and route it's ingress network
over WireGuard. For some reason it's not working: internal load balancer
fails to access containers from other nodes. So it's impossible to reach
containers from other nodes, load balancing/routing mesh becomes completely
broken.
Setup is pretty basic and everything works like a charm but this particular
feature. I also found few related questions, so there are number of people
interested in fixing this:
https://stackoverflow.com/questions/52409012/docker-swarm-mode-routing-mesh-not-working-with-wireguard-vpn
https://github.com/moby/moby/issues/37985
https://github.com/moby/moby/issues/36689 (that's my issue, more details
here)
Of course, I do understand that this could be Docker-specific issue, so I'm
just asking here for some directions:
- Does someone succeeded at enchancing Docker Swarm with WireGuard?
- My it be netns-related thing? Should we place Docker ingress network and
wg0 interface into same namespace?
Any help appreciated.
--
Best regards,
Kirill Kovalev
[-- Attachment #1.2: Type: text/html, Size: 1876 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2018-11-19 19:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAAWPTbOG8=XEwB-rCs9i2JYuMoJM-J_5RR4U2S_W4F+4katc_g@mail.gmail.com' \
--to=kovalev.kirill.a@gmail.com \
--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).