Skip to content

Updating

Jump to bottom
sassanix edited this page Oct 30, 2026 · 3 revisions

sync-alt icon Updating

Contents

Before you update

  1. Back up. See Backup and Restore — a database dump plus the uploads folder. Updates are tested, but a backup is the only way back.
  2. Read the release notes for the version you are moving to, especially for breaking changes. Releases live on GitHub, and the changelog lists every change.

Docker Compose

From the directory containing your compose file:

docker compose pull
docker compose up -d

That is the whole update. On startup the container waits for the database and runs any pending migrations automatically, so the database is brought up to date for you. Watch the log to confirm:

docker compose logs -f warracker

Look for Running database migrations... followed by normal startup lines. Then open the app and check the version on the About page.

If the page still looks like the old version, hard-refresh: Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (macOS). Static files are cached for up to a year, so a stale-looking page after an update is almost always the browser cache — see Troubleshooting.

Choosing a version

Images are published to ghcr.io/sassanix/warracker:

  • main:latest — the newest release.
  • main:1.0.4 (and other plain version numbers, no v prefix) — a pinned release.

Pinning a version is the safer choice for a set-and-forget instance: you update when you choose to, after reading the release notes. latest is for tracking development closely.

Unraid

Update from the Docker tab (or Community Apps) the same way as any other container: check for updates and apply. Your data lives in the appdata volumes, so updating the image does not touch it — but back up first anyway (see Backup and Restore).

Automatic updates

Tools like Watchtower can pull and recreate the container automatically. That works, but it skips the "read the release notes" step — if you use one, keep automated backups so a bad update is recoverable.

Rolling back

Database migrations only run forward. If you roll the image back to an older version, the database may be ahead of what that version expects. The reliable way back is to restore from the backup you took before updating (see Backup and Restore), not to just pull the old image.

Clone this wiki locally