Install Central Lite
Run Central Lite, the fleet control plane, from its tarball as an unprivileged account.
Built, not yet claimed preview: Central Lite has not passed its release gate.
From the tarball
Central Lite is one Linux binary, garm-central, with the fleet console built in, behind one HTTPS port. Download garm-central-X.Y.Z-<target>.tar.gz for x64 or ARM64 from the download page and verify it. Run it as an unprivileged account, never as root, that owns Central Lite's state directory: /var/lib/agentgarm-central unless you pass --state-dir to every command. That account cannot create a directory under /var/lib, so the first line, run from it, has root create it for the account; Central Lite refuses the directory unless it is 0700 and the account's.
sudo install -d -o "$(id -un)" -m 0700 /var/lib/agentgarm-central
mkdir -p ~/.local/opt && tar -xzf garm-central-X.Y.Z-<target>.tar.gz -C ~/.local/opt
export PATH="$HOME/.local/opt/garm-central-X.Y.Z-<target>/bin:$PATH" # and in the account's shell profile
garm-central init --url https://central.example:8443
garm-central root lite
garm-central admin bootstrap
garm-central serve --listen 0.0.0.0:8443init creates the org, its keys and the node certificate authority; --url is the address nodes and browsers reach. admin bootstrap prints a one-time code for the console's first admin. serve answers until it is stopped, so keep it running under your own service manager: the tarball ships no service unit. Keys are held in a software keystore in the state directory unless the host has an OS keystore; garm-central status names each key's custody.
The container image, once a release carries it
The tarball carries the image's definition, but no release ships the image yet: its base is not pinned. Once one does, it runs read-only as uid 65532, keeps everything, keys included, in one volume, and listens on 8443:
docker load -i garm-central-X.Y.Z-x86_64-unknown-linux-gnu-image.tar
docker volume create central
docker run --rm --read-only -v central:/var/lib/agentgarm-central garm-central:X.Y.Z init --url https://central.example
docker run --rm --read-only -v central:/var/lib/agentgarm-central garm-central:X.Y.Z root lite
docker run --rm --read-only -v central:/var/lib/agentgarm-central garm-central:X.Y.Z admin bootstrap
docker run -d --name central --read-only -v central:/var/lib/agentgarm-central -p 443:8443 garm-central:X.Y.ZThe image has no git, which the policy repository pull needs; until it does, run that from the tarball on a host that has git. In a container, keys are always held in software.
Next
Stand up Central Lite: the first admin and the first backup; then enrol developer machines.