[BUG] ZeroTier does not work in 3.1.1
PassiveLemon opened this issue · comments
I probably should have seen this coming but zerotier-one(1.10.2) was removed in Alpine 3.17, but currently we are using Alpine 3.20. In the image I download it from 3.16 and install it but the GitHub action fails at this step due to untrusted signatures, so the image never finishes building and isn't pushed to Dockerhub. I don't know why it works locally but that's a different issue.
I am now trying to refactor the Dockerfile to build ZT from source and I've encountered a strange issue. Zoraxy appears to get the controller ID but when I press the button to create a new network, nothing happens and I don't see any error messages in the Zoraxy logs.
I was afraid the problem had to do with Alpine's musl, so I installed libc6-compat and libstdc++ to provide compatibility, otherwise ZT fails with unrecognized symbol errors. This did not solve it. Currently I attempted to mitigate this by building everything on Debian derivatives but I actually have the same issue.
Was any of the ZeroTier stuff modified in 3.1.1? Does Zoraxy currently support ZeroTier 1.14.0?
I tested the latest zerotier in a Debian VM and I notice it is kinda broken.
- I can list the zerotier node ID, but cant create / list any network
- zerotier-cli is working and curl access of the API endpoint is working
- Zoraxy v3.1.1 works on zerotier v1.8.3 and v1.10.1
I will investigate further to see what might be the issue here.
After building like 6 versions of ZeroTier, it seems like the issue starts at version 1.12.0, which just so happens to have an ungodly changelog, so something probably changed in that version.