So I'm not running it on each individual container.
Instead I'm running with a guarantee of at least one tinc container on each
coreos host and then connect to other containers(currently have about 20
hosts running across the world with this setup)
I find on the whole setup to work well, I'm not noticing any unusual
overhead, but there is a lot of extra provisioning work I'm doing with
ansible which I will at some point put on GH as well.
https://github.com/botto/docker-tinc is what I'm using, there is a lot more
work to do, it's just a wrapper really at the moment, but do take note of
the run.sh file if you decide to write your own.
I'll probably move it to alpine soon, ubuntu is quite bloaty.
It would be interesting to use this as a solution to resolving containers.
Martin
On 17 April 2016 at 08:32, John Griessen <john at industromatic.com>
wrote:
> I'd like to hear from anyone using coreos to run a container with tinc
for
> purpose of connecting containers. Sounds almost like a chicken/egg
> problem:-)
>
> I'm thinking of running a container with alpine linux and tinc
installed
> there.
>
> John Griessen
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20160417/f80232d0/attachment.html>