-
v0.10.8 — application backup, image update and restore
Release / version (push) Canceled after 0sRelease / frontend (push) Canceled after 0sRelease / linux (amd64) (push) Canceled after 0sRelease / linux (arm64) (push) Canceled after 0sRelease / windows (push) Canceled after 0sRelease / macos (push) Canceled after 0sRelease / release (push) Canceled after 0sBuild and Push Docker Image / build-and-push (push) Canceled after 0sreleased this
2026-09-06 10:10:51 +03:00 | 67 commits to main since this releaseBack up, update and restore the compose applications node-stats already
discovers, from the Applications page.- restic engine, installed on demand into the data volume (pinned 0.19.1,
SHA256-verified) rather than baked into the image - repository backends: filesystem, SFTP (also how a Synology NAS is used)
and S3; SSH/S3 are cluster-wide in the connector registry, a filesystem
repository is node-local and named by its HOST path — node-stats mounts
it into itself through the controller instead of asking for compose edits - encryption can be declined explicitly, so snapshots restore with nothing
but the restic binary - jobs run in a short-lived helper container with identity mounts for only
the paths they declared, on the image the node itself runs; the
controller's standing privileges do not grow - backup: stop, snapshot compose files and every data location, start
update: snapshot, rewrite image tags keeping a .bak, pull, start
restore: down, erase, restic restore, start — data AND pinned versions - per-service version picker warning proportionally, snapshots newest
first with sizes, run history with live progress
Also: docker beta now reports its version instead of a commit hash, and
helper containers no longer fall back to the published default image.Verified end to end against a real docker daemon and a real restic.
Downloads
- restic engine, installed on demand into the data volume (pinned 0.19.1,