BackupZit in Docker
The console is now also published as a container image, ghcr.io/max-zit/backupzit, built from the same signed server package as the appliance and the Linux packages (including the agent installers it offers). The image is minimal — only the console, CA certificates and time zones, no shell — and runs as an unprivileged user. Run it with PostgreSQL through Docker Compose — docker-compose.yml and .env.example are in the repository under packaging/docker:
docker compose up -d
docker compose exec backupzit backupzit-server --initial-password
Agents are installed on the computers as usual and connect to port 8443 of the Docker host.
Updates: the console checks for new versions and shows them under Settings → Updates with the commands to run (docker compose pull and docker compose up -d). Before a new version changes the database, it keeps a copy of the console (the last three) in the data volume; --restore-pre-upgrade brings it back with the previous image. After an update the agents are updated from the console as always (automatically, when that is turned on). Tags: latest for official releases, testing for release candidates, or a version number.
The guide (Installation → Docker) is updated in all 14 languages.
Releases are signed with the BackupZit release key; consoles verify them before installing, and the container image is built only from a package whose signature and checksum were verified.