-
Notifications
You must be signed in to change notification settings - Fork 77
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
Use latest derper package #16
Comments
I concur. |
Another idea is to tag the images (e.g. |
Im not so sure about the tagging stuff. Since the repo on Docker Hub is tagged automatically with the trail tag in github action. Well, it's either someone create a pull and wait for the author to merge |
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 |
tailscale/tailscale@210264f
Tailscale said that when we run derper with
--verify-clients
, thederper
binary andtailscaled
binary on the machine must be built from the same git revision, which means the same version.derper-docker/Dockerfile
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
.The text was updated successfully, but these errors were encountered: