-
Notifications
You must be signed in to change notification settings - Fork 79
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
Docker container has Tailscale version “1.72.1-ERR-BuildInfo” #140
Comments
hmm, this does seem to be a newer behavior. I see it as well in my homelab with the latest container image. Previously, we had version numbers similar to Relevant code for these strings is https://github.com/tailscale/tailscale/blob/aeb15dea3032c0560793190731dd6a06b45850b2/version/version.go#L86-L102 @awly have you seen this with other tsnet apps? I doubt it would have had anything to do with #137, since we didn't actually change how we build the golink binary itself. |
I don't think this behavior is golink specific, or at least I have observed the same |
Without the git CLI, `go build` will not produce the embedded VCS metadata that's used to report the commit hash in node version string. This fixes the `1.72.1-ERR-BuildInfo` version string reported to Tailscale. Fixes #140
In this case, we were missing |
Without the git CLI, `go build` will not produce the embedded VCS metadata that's used to report the commit hash in node version string. This fixes the `1.72.1-ERR-BuildInfo` version string reported to Tailscale. Fixes #140 Signed-off-by: Andrew Lytvynov <[email protected]>
I use the docker container
ghcr.io/tailscale/golink:main
and I just updated to the latest version. When I go to my Tailscale Admin page, I see that the Tailscale version is listed as “1.72.1-ERR-BuildInfo”.That doesn’t strike me as a useful version number and it seems like something is broken in the release pipeline; can you fix it?
The text was updated successfully, but these errors were encountered: