Upgrade nightshipd

Move nightshipd to a new version without losing data. The data directory stays put — only the binary or image changes.

Back up first.

An upgrade shouldn’t touch your data, but take a fresh copy of the data directory before you start — see Back up and restore.

Docker / Compose

docker compose pull
docker compose up -d

The named volume persists; the new image starts against the same /data.

Docker Desktop

Pull the new latest, then recreate the container on the same named volume (nightship-data). Recreating on a fresh volume would start an empty server — the volume is the whole point.

Bare-metal (systemd)

Extract the new binary from the image, swap it in, and restart:

docker pull ghcr.io/nightship-io/nightshipd:latest
docker create --name nightshipd-extract ghcr.io/nightship-io/nightshipd:latest
docker cp nightshipd-extract:/usr/local/bin/nightshipd ./nightshipd
docker rm nightshipd-extract
sudo install -m 0755 ./nightshipd /opt/nightship/bin/nightshipd
sudo systemctl restart nightshipd

The evaluation clock is measured from the build date, so a newer unlicensed build restarts the trial — but install your production license anyway (Licensing). And keep the client and CI’s nightship-tide roughly in step: the installer bundles the matching CLI, and the CI composite action pins a version.

← All guides