2 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Michael StapelbergandBrad Fitzpatrick	64ab0ddff1	cmd/tailscale/cli: only exit silently if len(args) == 0 ... This amends commit b7e48058c8. That commit broke all documented ways of starting Tailscale on gokrazy: https://gokrazy.org/packages/tailscale/ — both Option A (tailscale up) and Option B (tailscale up --auth-key) rely on the tailscale CLI working. I verified that the tailscale CLI just prints it help when started without arguments, i.e. it does not stay running and is not restarted. I verified that the tailscale CLI successfully exits when started with tailscale up --auth-key, regardless of whether the node has joined the tailnet yet or not. I verified that the tailscale CLI successfully waits and exits when started with tailscale up, as expected. fixes https://github.com/gokrazy/gokrazy/issues/286 Signed-off-by: Michael Stapelberg <michael@stapelberg.de>	2025-01-13 11:27:35 -08:00
Michael StapelbergandBrad Fitzpatrick	2a6c237d4c	net/dns: overwrite /tmp/resolv.conf on gokrazy ... Appliances built using https://gokrazy.org/ have a read-only root file system, including /etc/resolv.conf, which is a symlink to /tmp/resolv.conf. The system’s dhcp client overwrites /tmp/resolv.conf instead, so we need to use this path in Tailscale, too. related to https://github.com/gokrazy/gokrazy/issues/209 fixes https://github.com/tailscale/tailscale/issues/8689 Signed-off-by: Michael Stapelberg <michael@stapelberg.de>	2023-07-23 09:53:32 -07:00