tailscale/gokrazy/tsapp
Brad Fitzpatrick 10d0ce8dde tstest/natlab: get tailscaled logs from gokrazy via syslog
Using https://github.com/gokrazy/gokrazy/pull/275

This is much lower latency than logcatcher, which is higher latency
and chunkier. And this is better than getting it via 'tailscale debug
daemon-logs', which misses early interesting logs.

Updates #13038

Change-Id: I499ec254c003a9494c0e9910f9c650c8ac44ef33
Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>
2024-08-13 07:56:29 -07:00
..
builddir tstest/natlab: get tailscaled logs from gokrazy via syslog 2024-08-13 07:56:29 -07:00
config.json tstest/natlab/vnet: add start of virtual network-based NAT Lab 2024-08-07 09:37:15 -07:00
README.md gokrazy: add prototype Tailscale appliance, build tooling, docs 2024-06-03 15:01:19 -07:00
usr-dir.tar gokrazy: add prototype Tailscale appliance, build tooling, docs 2024-06-03 15:01:19 -07:00

Tailscale Appliance

This is the definition of the Gokrazy Tailscale Appliance (tsapp) image. See the parent directory for context.

File contents

The config.json is a Gokrazy config.

The usr-dir.tar is a single symlink named bin pointing to /user. We write it to /usr/bin => /user so the Busybox ash shell's default $PATH includes /user, where the tailscale CLI is.

The builddir is the Gokrazy build environment, defining each program's go.mod.