Wiki· Updated 19 Oct 2026

The rs command: managing a service

Status, logs, backups, upgrades, IP access, stopping and removing RunStack services.

After install the server has the rs command. Replace <service> with its name: vault, vaultwarden, n8n, open-webui, uptime-kuma, outline, immich (all — rs list). Server scripts — rs info, rs slow, rs security, rs clean, see the wiki section.

Command	What it does
`rs <service> status`	state, address, version and available update
`rs <service> logs`	live logs
`rs <service> backup`	backup to `<dir>/backups`, the last 14 kept
`rs <service> upgrade [version]`	backup → new version; no version — the latest stable
`rs <service> access "1.2.3.4, 10.0.0.0/8"`	allow only these IPs; `off` — remove
`rs <service> stop` / `start`	stop / start, nothing is removed
`rs <service> restart`	restart
`rs <service> down`	remove the containers; data stays, `install` brings it back
`rs <service> purge`	full removal step by step with questions; backups are never deleted

Where things are

/opt/<service> (or the chosen directory) — .env with settings, compose.yml, data, secrets/, backups/.
/opt/runstack — installer code, the shared HTTPS proxy (Caddy) and links to the service directories.
/tmp/rs.log — detailed log of the last install (keys and tokens are not written to it).

Plain docker compose ps and docker compose logs also work in the service directory — it is the same project.

Updates

The service version changes only with rs <service> upgrade: a backup first, then the new version. Downgrades are refused — they can damage data.
The installer rs checks for a new release once a day and tells you how to update: run the command from the service page, replacing the trailing sudo bash with sudo bash -s -- --yes — settings and data are kept.