Skip to content

Arkive 0.4.0

Choose a tag to compare

@islamdiaa islamdiaa released this 30 Oct 18:51
· 47 commits to main since this release
1c2c915

Arkive 0.4.0 is about one question: do my backups actually work? It follows a production audit that found v0.2.4 reporting success for months while backing up no databases at all, and it adds checks that don't rely on a backup run reporting its own failure.

docker pull islamdiaa/arkive:0.4.0

Upgrade by recreating the container with the same /config volume; database migrations run on start. See Upgrading from 0.2.x below.

Highlights

Knowing it works

  • Overdue-backup watchdog. A job whose last good backup is older than its schedule window turns the dashboard red and sends backup.stale alerts.
  • Heartbeat. Point Arkive at an Uptime Kuma push monitor or healthchecks.io. It pings only while every job is healthy, so you also hear about it when Arkive itself is down.
  • Weekly restore drills. Recent database dumps are restored from the latest snapshot and loaded into a throwaway, network-isolated container of the same database image.
  • No silent successes. A run that misses anything (a database, a path, a target, unreadable files, failed discovery) is partial, with the reason.

Backups

  • Every database in a PostgreSQL cluster is dumped, plus roles (pg_dumpall --globals-only).
  • Dumps are stored uncompressed by default, so restic deduplicates them: a large database adds only its changes to each snapshot.
  • SQLite copies from read-only mounts no longer drop data still in the write-ahead log.
  • Exclude a database from backups on the Databases page (for example an app cache that holds an exclusive lock).
  • Truncated dumps are detected and never replace the last good one; dump files publish atomically.

Recovery

  • Recovery kit: a one-time export of the encryption password, every repository location and the restore steps. The dashboard reminds you until you confirm you've saved it.
  • Keyfile guard: Arkive refuses to start if /config/.keyfile is missing or doesn't match the database, instead of silently creating a new key that would strand every stored secret.
  • Restores always land in /config/restores, so the data you protect can be mounted read-only.

Fixes

  • Weekday schedules (* * 1-5, * * 0) ran a day late; the weekly restore drill never ran.
  • The Docker client now reconnects after a startup timeout. In v0.2.4, one timeout disabled database dumps until the container was restarted.
  • Scheduled jobs that collide wait for each other instead of being skipped.
  • The restic host name is stable (no more container IDs splitting retention groups); old snapshots are re-labelled during weekly retention.
  • The light theme now works across the whole UI.

Security

  • Command injection in the snapshot browser (fixed). An authenticated API caller could pass a path that restic read as an option (--password-command). Because Arkive holds the Docker socket, this amounted to control of the host. User-supplied values are now passed after -- and validated.
  • API open before setup (fixed). Until the setup wizard ran, every API route was reachable without credentials. Now only the scans the wizard needs are open, and setup can be completed only once, even under concurrent requests.
  • Dependency updates for published advisories: cryptography 50.0.2, weasyprint 70.0, jinja2 3.1.6, python-multipart 0.0.32, apprise 1.13.1, pydantic-settings 2.16.2, zod 4.6.7.
  • restic 0.19.1 and rclone 1.75.2 (rebuilt with a current Go toolchain), plus Debian security updates in the image.
  • A security policy with private vulnerability reporting.

If you run v0.2.x on a network others can reach, upgrade.

Upgrading from 0.2.x

  • Recreate the container with the same /config volume. Migrations run automatically.
  • Keep /config/.keyfile. 0.4.0 refuses to start without the keyfile that encrypted your stored secrets. Set ARKIVE_ALLOW_NEW_KEYFILE=1 only if you intend to start over and re-enter them.
  • Mount data read-only (/mnt/user/appdata:/mnt/user/appdata:ro, /boot/config:/boot-config:ro); Arkive no longer needs to write there.
  • After upgrading, save the recovery kit (Settings → Recovery kit) and add a notification channel.

Full changelog: v0.2.4...v0.4.0