tailscale/gokrazy/tsapp
Brad Fitzpatrick 9f1d9d324d gokrazy/tsapp: remove builddirs packages that aren't in config.json
These three packages aren't in gokrazy/tsapp/config.json but
used to be. Unfortunately, that meant that were being included
in the resulting image. Apparently `gok` doesn't delete them or
warn about them being present on disk when they're moved from
the config file.

Updates #13038
Updates #1866

Change-Id: I54918a9e3286ea755b11dde5e9efdd433b8f8fb8
Signed-off-by: Brad Fitzpatrick <bradfitz@tailscale.com>
2024-08-13 10:32:43 -07:00
..
builddir gokrazy/tsapp: remove builddirs packages that aren't in config.json 2024-08-13 10:32:43 -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.