Package GuestKit as a Linux binary (remote build)

Ship a client tarball (guestkit + install/test scripts) without giving users deploy scripts.

What you get

guestkit-1.0.1-linux-amd64/
  guestkit              # CLI binary
  install.sh            # one-command install
  install-client-deps.sh
  test-host.sh          # qemu / nbd / GuestKit binary checks
  test-selftest.sh      # full GuestKit selftest
  test-package.sh
  uninstall.sh
  HOST_SETUP.txt
  PREREQUISITES.txt
  guestkit.env.example

Build

GitHub Release (tag v*): CI builds the same user tarball and attaches it to the release:

• guestkit-<version>-linux-amd64.tar.gz (+ .sha256)
• guestkit-<version>-linux-amd64-musl.tar.gz (+ .sha256)
• zyvor-vm-tools-linux-amd64.tar.gz, .deb, optional .iso (Zeus VM Tools agent)
• Docker images on GHCR: ghcr.io/zyvorai/guestkit-worker, zyvor-api, zyvor-ui tagged v<version>

See deploy/README.md for k3s deploy and CI E2E.

Remote Linux host:

./scripts/package-binary-remote.sh <ephemeral-ip> operator --fetch
./scripts/package-binary-remote.sh <ephemeral-ip> operator --reuse-build --skip-deps

Local / CI (after cargo build --release on Linux):

./scripts/package-binary-release.sh --build
./scripts/package-binary-release.sh --build --target x86_64-unknown-linux-musl

Environment:

Variable	Purpose
GUESTKIT_PACKAGE_DIR	Remote output dir (default ~/guestkit-dist)
GUESTKIT_PACKAGE_VERSION	Override version string
GUESTKIT_REMOTE_SKIP_SSH_CHECK=1	Skip SSH preflight

User install

tar xzf guestkit-*-linux-amd64.tar.gz && cd guestkit-*-linux-amd64
./install.sh
./test-host.sh
./test-selftest.sh --quick
./guestkit inspect /path/to/disk.qcow2

User uninstall

./uninstall.sh --yes
./uninstall.sh --yes --remove-dir

Host requirements (not Kubernetes)

GuestKit uses pure Rust disk access — legacy appliance tooling is not required.

• qemu-img (and optionally qemu-nbd for QCOW2)
• nbd kernel module (modprobe nbd max_part=16)
• lvm2, parted (LVM/encrypted guests)
• Read access to disk image files (QCOW2, VMDK, RAW, …)
• See HOST_SETUP.txt in the tarball

For full remote deploy from source, use ./scripts/deploy-remote.sh.