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.
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) |
peardock-server-VERSION-linux-ARCH.tar.gz from the rolling release/opt/peardock/peardock-serverpeardock and adds it to the docker group (for /var/run/docker.sock)/etc/systemd/system/peardock.service and optionally enables it/opt/peardock/.env (mode 600) — check this file after first start for your keyssudo systemctl status peardock
sudo journalctl -u peardock -f
# After first start — keys are in .env (preferred)
sudo grep -E '^(SERVER_PUBLIC_KEY|SERVER_SEED)=' /opt/peardock/.env
# SERVER_PUBLIC_KEY → share for viewer / paste in client
# SERVER_SEED → admin only (never give to operators)
# Operators → Access → Create invite → share full pd1. string
peardock-client-VERSION-HOST.tar.gzpeardock.app under ~/Applications (clears quarantine via xattr)~/.local/share/peardock, symlink in ~/.local/bin, desktop entrypd1. invite (operator)For binary downloads by platform, checksums, and release notes, see Releases. Source builds and production ops are in Quick start and Operator guide.