Denton Gentry

`/tmp/tailscale/tailscaled.sock` ``` [/share/CACHEDEV1_DATA/.qpkg/Tailscale] # ./tailscale -socket /tmp/tailscale/tailscaled.sock up ```

This might be better done as a separate repository at gitlab, rather than try to accommodate both here. I say this because it makes testing changes more difficult.

> This is probably the same issue as https://github.com/tailscale/corp/issues/9664 Which y'all won't be able to see, but says: "Currently if a client is set unattended from SYSTEM or a single...

It is probably possible but I don't think it would do what one would want. Docker Desktop Extension, even on macOS and Windows, runs a small Linux system in a...

You'll need to give some amount of detail for us to be able to look into it. A bugreport would be ideal, but the Tailscale IP address would at least...

By all means, please send a PR. It would need to be an optional function or configuration option, as some deployments (including ours) do want just a subset of repositories...

Are you familiar with https://github.com/gokrazy/gokrazy ? We've discussed using it to build an image for an RPi to be a subnet relay appliance

Re: gokrazy, though still appealing, it currently does not work well with tailscale because we shell out for utilities like iptables which gokrazy does not have.

[Route auto-approvers](https://tailscale.com/kb/1018/acls/#auto-approvers-for-routes-and-exit-nodes) might be useful for this, if one allows all of the private IP ranges likely to be encountered.

I promise that when work is done on this, we will update the issue. This idea is not currently being worked on.