Containly 2.2.0: backup and restore

Containly 2.2.0 brought the new Backups page (shortcut G R). It backs up the data of a stack, a single container or a single volume and restores it on the same host. Manual backups, restore and retention are free.

The essentials

• What is backed up: named volumes, the stack folder with Compose file and .env, and the container configuration with image digests.
• Back up now is on the Backups overview, in the stack list, in the stack inspector ("Backups" tab), on the container overview and on the Volumes page.
• Encrypted by default with AES-256-GCM and a key from your passphrase. The passphrase is never stored.
• Targets: a folder on the Docker host (default /var/backups/containly, also on TCP, SSH and agent hosts) or a folder inside the Containly container.
• Consistency: live, stop the containers during the backup, or pre and post hooks.
• Restore always starts with a preview. As a copy (nothing is overwritten) or replace (a safety backup is made first and pinned for 7 days).
• Open format: every set has a readable manifest.json and can be read without Containly with scripts/clbk-decrypt.mjs.
• Notifications backup.failed (on) and backup.succeeded (off).

In Settings, "Backup and restore" is now called Containly configuration: it backs up the configuration of Containly itself, not your data.

Schedules, S3 and SFTP arrived with Containly 2.3.0, see its announcement.

The full guide: Back up and restore data.