Closed ryancnelson closed 4 years ago
Thanks for the issue submission.
The -socket flag should work, but I am not sure when it was introduced to Tailscale. Did you define TSTAG environment variable during build? The default Tailscale version being compiled is quite old. Try setting TSTAG environment variable to v1.1.0 to build latest version of Tailscale.
Alternatively, you can grab the latest build from https://github.com/ivokub/tailscale-qpkg/actions/runs/241151056
The default socket location is not convenient as the file system is overwritten when firmware is updated and your suggested link removed.
On Mon, 7 Sep 2020, 07:37 Ryan Nelson, notifications@github.com wrote:
I just built the package with docker today (2020/9/6): installs fine... the README says to cd to the proper directory, then: "./tailscale -socket var/run/tailscale/tailscaled.sock up"
observed output: "[/share/CACHEDEV1_DATA/.qpkg/Tailscale] # ./tailscale -socket var/run/tailscale/tailscaled.sock up flag provided but not defined: -socket USAGE tailscale subcommand [flags]
This CLI is still under active development. Commands and flags will change in the future. "
... doing a little debugging, i figured out that the default path for the socket it's trying is "/var/run/tailscale/tailscaled.sock"
adding a symlink, like "ln -s /share/CACHEDEV1_DATA/.qpkg/Tailscale/var/run/tailscale/ /var/run/tailscale" made the existing socket appear in the expected place, and now "./tailscale up" works properly.
should the "-socket" flag work? it should be either made to work, or the README should be corrected.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ivokub/tailscale-qpkg/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJ7S6U7RZ2AUKD3ADWRWHDSERPPPANCNFSM4Q5NRN5A .
Closing due to inactivity.
I just built the package with docker today (2020/9/6): installs fine... the README says to cd to the proper directory, then: "./tailscale -socket var/run/tailscale/tailscaled.sock up"
observed output: "[/share/CACHEDEV1_DATA/.qpkg/Tailscale] # ./tailscale -socket var/run/tailscale/tailscaled.sock up flag provided but not defined: -socket USAGE tailscale subcommand [flags]
This CLI is still under active development. Commands and flags will change in the future. "
... doing a little debugging, i figured out that the default path for the socket it's trying is "/var/run/tailscale/tailscaled.sock"
adding a symlink, like "ln -s /share/CACHEDEV1_DATA/.qpkg/Tailscale/var/run/tailscale/ /var/run/tailscale" made the existing socket appear in the expected place, and now "./tailscale up" works properly.
should the "-socket" flag work? it should be either made to work, or the README should be corrected.