Use latest derper package
Opened this issue · 4 comments
Tailscale said that when we run derper with --verify-clients, the derper binary and tailscaled binary on the machine must be built from the same git revision, which means the same version.
Line 5 in 5c2d88f
Considering most of people use the latest version of tailscale, we may need to switch to tailscale.com/cmd/derper@latest.
I concur.
This happened to me as yesterday when i was trying to setup this image, and the latest Tailscale client ( pure linux , which version is v1.68.2).
As the result, logs said : The client rejected. due to mistch match binary.
With my limited knowledge with Dockerfile, it is kinda difficult for me to build the image with current v1.68.2 of tailscale client.
Another idea is to tag the images (e.g. v1.68.2 ) so they work with arbitrary tailscale versions.
Another idea is to tag the images (e.g.
v1.68.2) so they work with arbitrary tailscale versions.
Im not so sure about the tagging stuff.
Since the repo on Docker Hub is tagged automatically with the trail tag in github action.
I have tried several tag listed in the dev docker hub. It looks like that dev has deleted some of the recent images.
To be honest, i have not tried the latest tag which is push 4h ago.
Well, it's either someone create a pull and wait for the author to merge
or perhap, should clone the repo and redo the Dockerfile and then do the github action to get the correct image.
I've created a fork (https://github.com/hrz6976/derper-docker) that automatically checks for the latest Tailscale version every week, builds the derper image for that version, tags the image, and uploads to dockerhub. To try out:
docker pull hrz6976/derper:v1.68.2 # current latest version
docker run -e XXX=YYY hrz6976/derper:v1.68.2