I see --state is used rather than --statedir and it succeeded in creating a state file.
[/share/CACHEDEV1_DATA/.qpkg/Tailscale] # ls -al /share/CACHEDEV1_DATA/.qpkg/Tailscale/state/
drwxrwxrwx 2 admin administ 4096 Dec 29 20:32 ./
drwxr-xr-x 4 admin administ 4096 Dec 29 19:55 ../
-rw------- 1 admin administ 2250 Dec 29 20:32 tailscaled.state
Checking help:
Usage of ./tailscaled:
...snip...
-state string
absolute path of state file; use 'kube:<secret-name>' to use Kubernetes secrets or 'arn:aws:ssm:...' to store in AWS SSM; use 'mem:' to not store state and register as an ephemeral node. If empty and --statedir is provided, the default is <statedir>/tailscaled.state. Default: /var/lib/tailscale/tailscaled.state
-statedir string
path to directory for storage of config state, TLS certs, temporary incoming Taildrop files, etc. If empty, it's derived from --state when possible.
The help text suggesting If empty, it's derived from --state when possible but I guess currently it's not possible here yet.
I went ahead and edited my init script and that (after some hopefully unrelated dns troubleshooting) let me request a cert.
[/share/CACHEDEV1_DATA/.qpkg/Tailscale] # ./tailscale cert nas.actual-tailnet-redacted.ts.net
Wrote public cert to nas.actual-tailnet-redacted.ts.net.crt
Wrote private key to nas.actual-tailnet-redacted.ts.net.key
For a little extra confusion and maybe this belongs a bug over on the main repo but /var/lib/tailscale/ is getting created when starting the app. (I stopped, deleted it, and started again to make sure it wasn't left over from testing older community packages)
[/share/CACHEDEV1_DATA/.qpkg/Tailscale] # ls -al /var/lib/tailscale/tailscaled.log.conf
-rw------- 1 admin administ 209 Dec 29 21:07 /var/lib/tailscale/tailscaled.log.conf
Something logging related seems to save some state and doesn't care that the statedir isn't otherwise set when other features can't auto-select that same directory. And turns out even with statedir the way I changed it, it still writes this log.conf file there.
Like #62 I'm still using https://github.com/tailscale/tailscale-qpkg/releases/download/qnap-v1.34.1/Tailscale_1.34.1-1_arm-x41.qpkg
With
tailscale
up and running, I wanted to get an SSL certificate but instead got an error:Checking how
tailscaled
was launched:I see --state is used rather than --statedir and it succeeded in creating a state file.
Checking help:
The help text suggesting If empty, it's derived from --state when possible but I guess currently it's not possible here yet.
I went ahead and edited my init script and that (after some hopefully unrelated dns troubleshooting) let me request a cert.
For a little extra confusion and maybe this belongs a bug over on the main repo but
/var/lib/tailscale/
is getting created when starting the app. (I stopped, deleted it, and started again to make sure it wasn't left over from testing older community packages)Something logging related seems to save some state and doesn't care that the statedir isn't otherwise set when other features can't auto-select that same directory. And turns out even with statedir the way I changed it, it still writes this log.conf file there.