Containly 2.5.0: anonymous volumes, SMB, NFS and restores to another host

Containly 2.5.0 is released. This version adds backups of anonymous Docker volumes, SMB and NFS backup targets, and restores to another Docker host.

New in 2.5.0

• Back up anonymous volumes: Container and stack backups include anonymous volumes by default, with per-plan and manual backup opt-outs. They are identified by container name and mount path instead of the random volume name. Database dumps work on them too. Older backup sets remain readable.
• SMB and NFS (Pro): SMB3 with mandatory session encryption and NFSv4/v4.1 are available as backup targets, including connection tests. Configuration is available in English, German and Spanish.
• Restore to another host (Pro): Restore containers, volumes and Compose stacks as a copy or by replacing the destination on another Docker host. Replacing takes a safety backup on the destination first. The source host is never changed. Unsafe host paths, privileged settings and external resources are refused before any writes.

Free and Pro

Free: manual backups and restores on the same host, all consistency modes including database dumps, encryption, manual verification, retention, local and host-path targets, notifications, and download and import of .clbk files onto Free targets. Anonymous volumes are included in Free too.

Pro: schedules, scheduled verification, creating and editing S3/SFTP/SMB/NFS targets, writing and importing onto those targets, and restoring to another host. After a Pro licence expires, existing sets on those targets can still be listed, verified, downloaded and restored to the same host. Scheduled backups pause until a valid Pro licence is active again.

SMB requirements

SMB requires Linux 6.7 or newer, Landlock and Docker's default seccomp profile. The confined SMB client can only reach the validated server. Without Landlock, the connection test explains the requirement and SMB fails closed. There is no unconfined fallback.

Other improvements

Backup progress no longer reaches 100% while a run is still active. Host system files are skipped without misleading backup warnings. The unchanged local Docker host name follows the interface language. Update checks and notifications only consider newer versions, and older release notes are no longer shown. Full translated notification details appear in a desktop tooltip and wrap to two lines on touch screens.

Update

Set the image in your Compose file to amslertec/containly:2.5.0, then run in that Compose directory:

docker compose pull && docker compose up -d

Full release notes on GitHub