-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No persistent data variable/option for the docker-container #2310
Comments
sorry it's not easier to find |
Hmm, maybe my English is not good enough for this, I try again. In addition: The config also relates to the config save path on all the systems but not in docker. |
It doesn't have persistent storage as far as I know, but you can pass in the identity and joined networks to get the same result.
|
If you're using the official ZeroTierOne Docker image you can assign a persistent storage volume to keep your node identity and configuration around using a normal Docker volume mapping. Ex.: docker run \
--net=host \ # create network interface in host OS namespace, not just inside the container
--device=/dev/net/tun --cap-add=NET_ADMIN \ # allow access to the TUN/TAP virtual device so new interfaces can be created
-v ./zt1-data:/var/lib/zerotier-one \ # mount the zt1-data directory under /var/lib/zerotier-one inside the container
zerotier/zerotier # official ZT1 client image That should spawn an instance inside a container with its state persisted to the |
Hey there :)
What you expect to be happening.
Having a variable/option to set the directory for persistent data:
Trying to use your service with truenas scale and the docker image of zerotier provided by truenas Charts. Unfortunately there is no option to set a variable/path for persistent data. There is also not a single word about persistent data in the docker-readme. I also haven’t been able to find any other place in GitHub mentioning it, besides the non-docker Version for Win/Mac/Linux…
What is actually happening?
Every time I reboot/update the docker has a clean container which won’t connect because ist is not authorized and always provided with a new docker-zerotier-id.
Any steps to reproduce the error.
Install the scontainer on truenas scale with their integrated docker manager (Charts). Every restart it is empty beside the zerotier id configured.
Any relevant console output or screenshots.
What operating system and ZeroTier version. Please try the latest ZeroTier release.
Truenas Scale 24.04.1.1 / Zerotier 1.14.0
I opened a bug on truenas. The devs said they are using the official docker u provide and would be happy to add the variables needed.
https://ixsystems.atlassian.net/browse/TNCHARTS-1144
Or on the other hand, can u tell me why u don't mention it in ur docs at all? Maybe it is a feature and not a bug and I’m not getting the point of it ;)
Thanx in advance
N3331N
The text was updated successfully, but these errors were encountered: