There are currently 111 ZeroTier-related images on Docker Hub, with none of them belonging to the ZeroTier dockerhub user. This can cause a lot of headaches for people that see 'Docker' listed on the downloads page, as they might pick a random image to use without checking if a version mismatch, whether the Dockerfile was modified from the origin source before building, etc.
It also means there's not a good way to add an Unraid app template to the ZeroTierNAS repo, as you'd be relying on a third party's docker image. Having to double/triple check all these things to install a security-focused app is not ideal.
As mentioned, there's already a Dockerfile in the repo, so it would be nice if the container image creation/versioning/hosting were added to the existing CI pipeline. That way there would be an image available with version/build parity to other releases, and it could be trusted.
The other alternatives already exist (i.e. building/hosting a copy ourselves), which work, but are non-ideal IMO due to my previous concerns.
This process could be added to the Jenkinsfile (not sure how you're handling CI behind the scenes though), but adding a trigger in docker hub to build on a new release would be easiest. Would just need to specify the Build Context since the Dockerfile isn't in the root directory. Here are the triggers/regexes I use to set the image version (and latest) tags based on the v1.2.3 naming scheme.
(Apologies if you already know all of this)

yes please!
+1 please make sure to provide official image as part of the 1.6.0 release!
I found zerotier has joined Docker Hub in Sep 2015, and it published zerotier/zerotier-containerized several years ago. I don't know why these all were removed.
I'm really looking forward a official zerotier image to build my moon node.
Most helpful comment
+1 please make sure to provide official image as part of the 1.6.0 release!