Install Bothy

Four commands on a Linux machine that already has Docker. Read each one first; none of them needs root.

Newest release: v2026.11.2, published November 17, 2026. Release page

The lab proof ran release 2026.11.2.

Before you start

  • A Linux machine, amd64, with Docker and the Compose v2 plugin. bothy install checks both and stops with the exact fix if one is missing.
  • Enough free memory for the stack’s limits (the preflight checks this) and a free port 80. Move it with --port; expose it beyond this machine with --bind 0.0.0.0 (it listens on 127.0.0.1 by default).
  • Your user must be able to run docker without sudo. Bothy never calls sudo.
  1. Download the binary and the checksums

    Both are release assets. The archive holds one file, bothy.

    Download the binary and the checksums
    curl -fsSLO https://github.com/YehudaBriskman/Bothy/releases/download/v2026.11.2/bothy_2026.11.2_linux_amd64.tar.gz
    curl -fsSLO https://github.com/YehudaBriskman/Bothy/releases/download/v2026.11.2/checksums.txt
    
  2. Verify what you downloaded

    The first command checks the archive against the release’s checksums.txt. The second checks that GitHub attested the build; it needs the gh command and is optional, but it is the one that ties the file to this repository.

    Verify what you downloaded
    sha256sum --ignore-missing -c checksums.txt
    gh attestation verify bothy_2026.11.2_linux_amd64.tar.gz --repo YehudaBriskman/Bothy  # optional
    
  3. Put it on your path

    Any directory on your PATH will do. ~/.local/bin needs no root.

    Put it on your path
    tar -xzf bothy_2026.11.2_linux_amd64.tar.gz
    install -D -m 0755 bothy ~/.local/bin/bothy
    bothy version
    
  4. Read the plan, then install

    The dry run prints the plan and the preflight results and changes nothing. The real run prints the address when it is up.

    Read the plan, then install
    bothy install --dry-run  # prints the plan, changes nothing
    bothy install
    

    It prints Bivvy is up with the address. Open it in a browser on the same machine, or on another if you passed --bind.

Afterwards

  • bothy install again is safe: finished steps are skipped, and an interrupted run resumes.
  • To move to a newer release, download that release’s binary and run bothy update. It verifies the new release, keeps the previous generation, and rolls back if the new one does not come up healthy.
  • bothy uninstall stops the stack and removes what it generated. Your data, your secrets and the pulled images stay. bothy uninstall --purge deletes them too, after you type a confirmation phrase.

Which archive

Every release carries these. Only the first row is supported for running a stack.

SystemArchiveStatusSizeSHA-256
darwin/amd64bothy_2026.11.2_darwin_amd64.tar.gzCommand-line client only3.6 MBf0e1d1eb2c73ee42137e472181b088b5626704277d5f7363d1b079fb3f06d240
darwin/arm64bothy_2026.11.2_darwin_arm64.tar.gzCommand-line client only3.3 MB730fb017baaac22186db1d1b9933a723502ee5bd05afd9dd742109f645dd7b8e
linux/amd64bothy_2026.11.2_linux_amd64.tar.gzRun end to end in the lab3.6 MB362c3b356f9a6d5fe4953f10fd13f33735447eac2c9320fa404d68619514c87e
linux/arm64bothy_2026.11.2_linux_arm64.tar.gzBuilt, never run3.2 MBb7eaf1cd191ce3f216ab777fb03be80f01d110babc6afc02c4196172fe7c8e23
windows/amd64bothy_2026.11.2_windows_amd64.zipCommand-line client only3.7 MB7b6368d0069d7cd85250ceb8601ddbb2cdf5194c04bbb5fd9808697a2e6fad2a
windows/arm64bothy_2026.11.2_windows_arm64.zipCommand-line client only3.3 MB9aa1e2cc1b9bb05f251562cf12d32fc8cf25641063a6135d5cacd3c53d028c4c

Not supported yet

  • Installing the larger sizes (Bothy, Basecamp, Cairn).
  • Running the stack on macOS or Windows. Those archives are clients only.
  • Running the arm64 build: it compiles and is attached to every release, but nobody has run it.
  • WSL, rootless Docker, and a system-wide install for a headless server.
  • A package for apt, dnf, Homebrew or winget.

Prefer to read a repository first?

There is an older path that clones the repository and runs just up. It starts the full development stack, not the small one, and the guide describes it. The installing guide. Source