diff options
| -rwxr-xr-x | .gitignore | 2 | ||||
| -rw-r--r-- | examples/docker/Dockerfile | 19 | ||||
| -rw-r--r-- | examples/docker/README.md | 8 | ||||
| -rw-r--r-- | examples/docker/main.sh | 25 |
4 files changed, 54 insertions, 0 deletions
@@ -29,6 +29,8 @@ Thumbs.db # *nix/Mac build droppings /build-* /ZeroTierOneInstaller-* +/examples/docker/zerotier-one +/examples/docker/test-*.env # Miscellaneous file types that we don't want to check in *.log diff --git a/examples/docker/Dockerfile b/examples/docker/Dockerfile new file mode 100644 index 00000000..a4274924 --- /dev/null +++ b/examples/docker/Dockerfile @@ -0,0 +1,19 @@ +FROM centos:7 + +MAINTAINER https://www.zerotier.com/ + +RUN yum -y update && yum clean all + +EXPOSE 9993/udp + +RUN mkdir -p /var/lib/zerotier-one +RUN mkdir -p /var/lib/zerotier-one/networks.d +RUN ln -sf /var/lib/zerotier-one/zerotier-one /usr/local/bin/zerotier-cli +RUN ln -sf /var/lib/zerotier-one/zerotier-one /usr/local/bin/zerotier-idtool + +ADD zerotier-one /var/lib/zerotier-one/ + +ADD main.sh / +RUN chmod a+x /main.sh + +CMD ["./main.sh"] diff --git a/examples/docker/README.md b/examples/docker/README.md new file mode 100644 index 00000000..4dae52f3 --- /dev/null +++ b/examples/docker/README.md @@ -0,0 +1,8 @@ +Simple Dockerfile Example +====== + +This is a simple Docker example using ZeroTier One in normal tun/tap mode. It uses a Dockerfile to build an image containing ZeroTier One and a main.sh that launches it with an identity supplied via the Docker environment via the ZEROTIER\_IDENTITY\_SECRET and ZEROTIER\_NETWORK variables. The Dockerfile assumes that the zerotier-one binary is in the build folder. + +This is not a very secure way to load an identity secret, but it's useful for testing since it allows you to repeatedly launch Docker containers with the same identity. For production we'd recommend using something like Hashicorp Vault, or modifying main.sh to leave identities unspecified and allow the container to generate a new identity at runtime. Then you could script approval of containers using the controller API, approving them as they launch, etc. (We are working on better ways of doing mass provisioning.) + +To use in normal tun/tap mode with Docker, containers must be run with the options "--device=/dev/net/tun --cap-add=NET_ADMIN". The main.sh script supplied here will complain and exit if these options are not present (no /dev/net/tun device). diff --git a/examples/docker/main.sh b/examples/docker/main.sh new file mode 100644 index 00000000..e9febb13 --- /dev/null +++ b/examples/docker/main.sh @@ -0,0 +1,25 @@ +#!/bin/bash + +export PATH=/bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin + +if [ ! -c "/dev/net/tun" ]; then + echo 'FATAL: must be docker run with: --device=/dev/net/tun --cap-add=NET_ADMIN' + exit 1 +fi + +if [ -z "$ZEROTIER_IDENTITY_SECRET" ]; then + echo 'FATAL: ZEROTIER_IDENTITY_SECRET not set -- aborting!' + exit 1 +fi + +if [ -z "$ZEROTIER_NETWORK" ]; then + echo 'Warning: ZEROTIER_NETWORK not set, you will need to docker exec zerotier-cli to join a network.' +else + # The existence of a .conf will cause the service to "remember" this network + touch /var/lib/zerotier-one/networks.d/$ZEROTIER_NETWORK.conf +fi + +rm -f /var/lib/zerotier-one/identity.* +echo "$ZEROTIER_IDENTITY_SECRET" >identity.secret + +/var/lib/zerotier-one/zerotier-one |