Dmitry Spikhalskiy

The image was upgraded to Zerotier 1.12.0 UPD Aug 27: Zerotier 1.12.1

The above solution originally published by @Vivent that includes setting "Include listening interfaces" works for me with the latest 6.12.4-rc18 and 6.12.4-rc19. unRaid UI, shares, and docker containers are fully available for other nodes in Zerotier virtual network again. Important, if you upgrade from 6.12.3 and have the listening interfaces already set up as suggested: wipe them out, save, and put your zerotier gateway name back again. It was a necessary step for me to make things work after 6.12.3 -> 6.12.4-rc18/19 upgrade.

There will be no updates from me here. There were no changes in the container and its configuration and the same exact container with the same exact configs continues to work successfully on Servers with other Linux distributions. So the problem is in the Unraid update and the fix if any will come from the Unraid team. What I personally observe, with the following Docker settings at least, Zerotier can connect to the service just fine, and other devices in the virtual network can successfully ping the Unraid virtual IP address. And I even can open a directory listing on <unraid virtual ip>:6080. But Unraid UI and docker container ports are not available for devices in the virtual network. My only guess is that 6.12 brought some unannounced changes in isolation causing it. iptables? nginx? I can't figure it out.

@Elmojo Shouldn't be happening. Next time it happens, try to check the logs of the container. They are available by clicking on the icon in the Docker tab and choosing Logs. Also, check the logs on your UnRaid server too around the time it happens. Some IO problem or a crash on your specific configuration may be causing it.

A repository this Dockerfile builds from is: https://github.com/Spikhalskiy/zerotier-unraid-docker and it's not archived. I archived repo with a Dockerfile that was actually building a base underlying image. Now there is an actively maintained zyclonite/zerotier image and I switched on it as a base image and just adapt it for Unraid.

@Demon1337 Thanks for the report! Yeah, during the last major upgrade of the container I indeed lost a docker ENTRYPOINT. I just released the fix, it should initialize as expected now.

Most users don't need to go into any directory or even open the cli. Please see the first post of this thread for a manual on how to use this container.

@Moepsindi Why do you run ./zerotier-cli at all? This container doesn't have runnable `zerotier-cli` in the root of the file system. So, this command is not expected to work. zerotier-cli executable is in `/usr/bin/zerotier-cli`. `zerotier-cli join` or `zerotier-cli info`, etc will work in this container.

@air1kdf this container does exactly that on every start. If this command helped you, you either put an incorrect networkId in the container settings or a simple restart of the container would also help.

@ilpixelmatto 4 days ago I upgraded the container from 1.8.2 to 1.10.2. If you want to check if that is what causes your instability, you may downgrade by specifying a tag "spikhalskiy/zerotier:1.8.2" and see how it behaves.

The image was upgraded to the latest Zerotier 1.10.2

This app/container works fine with Unraid 6.10.2 or 6.10.3, there is nothing to fix. You have to debug your own environment. In the root post you can find steps that you should do to make a meaningful information about your issue. Somebody in this thread may help if you provide enough info.

1.10.0? I will skip this one. 1. I see several issues in github that after an upgrade specifically to 1.10.0 users installations stopped working. I inclined to wait for at least first patch version. https://github.com/zerotier/ZeroTierOne/issues/1692 https://github.com/zerotier/ZeroTierOne/issues/1695 2. I'm not sure what's going on with 1.10.0. The latest code changes in zerotier github are for 1.8.10. There is neither Release Notes related to 1.10.0 (https://github.com/zerotier/ZeroTierOne/blob/master/RELEASE-NOTES.md), nor code changes between 1.8.10 - 1.10.0. I don't want to upgrade to some version that is stated just on their website and completely doesn't exist in the code repository. I guess it's ok if they suddenly went closed source, but it's not ok that I can't find any information or statement about it around at all.

Is there a problem 1.8.10 solves for you that 1.8.2 doesn't?

Yes, it's a custom image. First of all, it's on Alpine and it's much lighter. Zerotier official image moved to debian at some time, I took their image at that time and maintain myself: https://github.com/Spikhalskiy/zerotier-containerized/blob/master/Dockerfile Second, it has a custom starter script that wires parameters the right way: https://github.com/Spikhalskiy/zerotier-unraid-docker/blob/master/Dockerfile It doesn't have any changes to zerotier binaries and install them from the official sources. It's all on github, suit yourself.