rolling · 64-bit only

Download & install

Remote Docker without opening ports, exposing the Engine, or maintaining a VPN. The recommended path is the interactive install.sh script. It detects OS and arch, installs a Linux systemd server (with the docker group) or a desktop client, and pulls artifacts from the rolling release.

Install with curl Browse releases Gitea

One-line installer (recommended)

Interactive by default. Asks server vs client (or both). Server path is Linux-only for systemd; client works on Linux and macOS. Windows: download a .tar.gz from the rolling release.

curl -fsSL https://install.peardock.boats | bash

# Non-interactive
curl -fsSL https://install.peardock.boats | bash -s -- --server --yes
curl -fsSL https://install.peardock.boats | bash -s -- --client --yes
curl -fsSL https://install.peardock.boats | bash -s -- --both --yes

Flag / env	Meaning
`--server` / `-s`	Install peardock-server (Linux → `/opt/peardock` + systemd)
`--client` / `-c`	Install desktop client
`--both` / `-b`	Install both
`--yes` / `-y`	Non-interactive defaults
`--tag rolling`	Release tag (default: `rolling`)
`PEARDOCK_SERVER_DIR`	Server install path (default `/opt/peardock`)
`PEARDOCK_VERSION`	Pin asset version (default: auto from release)

What the installer does

Server (Linux)

Downloads peardock-server-VERSION-linux-ARCH.tar.gz from the rolling release
Installs binary to /opt/peardock/peardock-server
Creates system user peardock and adds it to the docker group (for /var/run/docker.sock)
Writes /etc/systemd/system/peardock.service and optionally enables it
State / seed in /opt/peardock/.env (mode 600)

sudo systemctl status peardock
sudo journalctl -u peardock -f
# Public key is printed on first start. Share it with clients.

Client

Downloads peardock-client-VERSION-HOST.tar.gz
macOS: peardock.app under ~/Applications (clears quarantine via xattr)
Linux: binary under ~/.local/share/peardock, symlink in ~/.local/bin, desktop entry

🖥 peardock-server

Bare standalone HyperDHT control plane. Run on the host with Docker. Identity from SERVER_SEED / .env.

Asset pattern: peardock-server-VERSION-HOST.tar.gz

linux-x64.tar.gz

linux-arm64.tar.gz

darwin-x64.tar.gz

darwin-arm64.tar.gz

win32-x64.tar.gz

win32-arm64.tar.gz

⌘ peardock-client

Desktop GUI (Electron). Connect with the server public key. Multi-peer fleet, tunnels, terminals, deploy wizard.

Asset pattern: peardock-client-VERSION-HOST.tar.gz

linux-x64.tar.gz

linux-arm64.tar.gz

darwin-x64.app in tar

darwin-arm64.app in tar

win32-x64.tar.gz

win32-arm64.tar.gz

Manual download

Browse all assets on the rolling release. Each tarball has a sibling .sha256 checksum.

# Example: Linux x64 server
curl -fLO https://git.ssh.surf/snxraven/peardock/releases/download/rolling/peardock-server-2.0.1-linux-x64.tar.gz
curl -fLO https://git.ssh.surf/snxraven/peardock/releases/download/rolling/peardock-server-2.0.1-linux-x64.tar.gz.sha256
sha256sum -c peardock-server-*.sha256
tar -xzf peardock-server-*.tar.gz
# → peardock-server binary

Build from source

git clone https://git.ssh.surf/snxraven/peardock.git
cd peardock
npm ci
npm run server          # control plane (needs Docker socket)
npm run start:client    # Electron GUI
# or
npm run make            # all 64-bit server + client hosts → out/

Node.js ≥ 20 required. See Quick start and Operator guide for production.

macOS Gatekeeper. Darwin clients from Linux CI are ad-hoc signed. If the app is blocked: right-click → Open, or xattr -cr ~/Applications/peardock.app. Developer ID re-sign: npm run sign:macos -- out/peardock-darwin-arm64/peardock.app

Docker access on the server. The service user peardock must reach /var/run/docker.sock (usually group docker, mode 660). The installer adds peardock to that group. If stats/start fail with permission errors: sudo usermod -aG docker peardock && sudo systemctl restart peardock (and restart Docker if the group was just created).