OUTDATED Host your own ZeroTier network controller and manage it via ztncui web UI
100K+
Host your own ZeroTier network controller and manage it via ztncui.
Screenshots available here: https://key-networks.com/ztncui/#screenshots.
Dockerfile: https://gist.github.com/mdPlusPlus/0f6285c6402aa4aff4aa4a9e5dfc38c0
Base image: ubuntu:latest
Uses UID and GID 2000
Port 3000 for HTTP access
Port 3443 for HTTPS access
Uses /var/lib/zerotier-one/ volume for ZeroTier config
Uses /opt/ztncui/src/etc/ volume for ztncui config (including TLS certificates)
Automatically creates self-signed TLS certificate if no other is present during start
Does not require --cap-add=NET_ADMIN
docker run -d --name ztncui -p 3443:3443 \
-v /path/to/zerotier_config/:/var/lib/zerotier-one/ \
-v /path/to/ztncui_config/:/opt/ztncui/src/etc/ \
mdplusplus/zerotier-network-controller-ui
Access web UI by visting https://localhost:3443/.
Change default password!
File system structure of the volumes will look like this after the first start:
$ sudo tree -ug /path/to/
/path/to/
├── [2000 2000 ] zerotier_config
│ ├── [2000 2000 ] authtoken.secret
│ ├── [2000 2000 ] controller.d
│ │ ├── [2000 2000 ] network
│ │ └── [2000 2000 ] trace
│ ├── [2000 2000 ] identity.public
│ ├── [2000 2000 ] identity.secret
│ ├── [2000 2000 ] peers.d
│ ├── [2000 2000 ] planet
│ ├── [2000 2000 ] zerotier-one.pid
│ └── [2000 2000 ] zerotier-one.port
└── [2000 2000 ] ztncui_config
├── [2000 2000 ] passwd
├── [2000 2000 ] storage
└── [2000 2000 ] tls
├── [2000 2000 ] fullchain.pem
└── [2000 2000 ] privkey.pem
I had some conflicts with UIDs and permissions on my Ubuntu host with the official ztncui Docker image.
This build automatically corrects permissions and can be built from only a single Dockerfile, no external build or startup scripts (transparency).
The official build also requires --cap-add=NET_ADMIN while this one does not.
Content type
Image
Digest
Size
198.4 MB
Last updated
over 6 years ago
docker pull mdplusplus/zerotier-network-controller-ui