jenserat/docker-tinc

tinc is a Virtual Private Network (VPN) daemon that uses tunnelling and encryption to create a secure private network between hosts on the Internet.

tinc for Docker

Dockerfile (c) 2015 Jens Erat, [email protected]
Licensed under BSD license

tinc is a Virtual Private Network (VPN) daemon that uses tunnelling and encryption to create a secure private network between hosts on the Internet.

This Dockerfile provides an image for running tinc 1.1 (pre release, as packaged by Debian).

Usage

The default entrypoint of the container is tinc, so you can directly issue commands to tinc, for example docker run jenserat/tinc init (which will run tinc init inside the container) to have tinc create the basic configuration for you. Tinc's configuration is persisted as a volume, you can also share a host folder in /etc/tinc.

tinc requires access to /dev/net/tun. Allow the container access to the device and grant the NET_ADMIN capability:

--device=/dev/net/tun --cap-add NET_ADMIN

To make the VPN available to the host, and not only (linked) containers, use --net=host.

A reasonable basic run command loading persisted configuratino from /srv/tinc and creating the VPN on the host network would be

docker run -d \
    --name tinc \
    --net=host \
    --device=/dev/net/tun \
    --cap-add NET_ADMIN \
    --volume /srv/tinc:/etc/tinc \
    jenserat/tinc start -D

Everything following start are parameters to tincd, -D makes sure the daemon stays active and does not actually daemonize, which would terminate the container.

Administration and Maintenance

Instead of passing start as tinc command, you can also execute arbitrary other tinc commands. Run help for getting a list, of read the tinc documentation.

To enter the container for various reasons, use docker exec, for example as docker exec -ti [container-name] /bin/bash.

Image Updates

The image is linked to the official Debian images, and automatically rebuild whenever the base image is updated. tinc is fetched from the Debian experimental repositories (where tinc 1.1 pre release versions are available).

docker-tinc's Issues

Container stops immediately and no config files are created

As the title says.
Running:
Docker version 18.09.2, build 6247962
Ubuntu 18.10
latest tinc dockerfile
All running in a vultr vps

I run this command:

docker run -d \
    --name tinc \
    --net=host \
    --device=/dev/net/tun \
    --cap-add NET_ADMIN \
    --volume /srv/tinc:/etc/tinc \
    jenserat/tinc start -D

as root and it creates the containers, but when doing docker container ls --all, they are all exited and have stop codes, tinc is '1'. And there is no form of any config created anywhere, I even created the tinc folder in etc and chown'ed it to no avail.

User is fixed to nobody

Thanks for the Dockerfile, it makes deployment very sweet.

I'm doing some routing so I need to manipulate the route tables for which is root access required. I see that tinc is running under user nobody. Is it possible to make it overwritable (via an env var for example)?