Knowledge base / Operation
Updates
Install a new version and go back if needed.
Procedure
-
Create a backup: Administration → Settings → Manage backups → Back up now.
-
Get the new version:
docker pull <registry>/contracthub:<new-version>Without internet access, load the bundle of the new version with
docker load, see Installation. -
Enter the version: In
compose.yamlchange theimage:line of the servicecontracthubto the new version. -
Restart:
docker compose up -d docker compose logs -f contracthub
The database is brought up to date automatically at startup. The log shows the new version.
In the browser
Open browsers detect the new version and show “A new version is available”. One click on Reload is enough. If a browser is stuck, User menu → Clear cache and reload helps.
The running version is shown at the bottom of the sidebar. Clicking it opens the changelog.
Back to the previous version
An update changes the database. The way back therefore goes through the backup from before the update:
-
Enter the previous version in
compose.yamland rundocker compose up -d. -
Restore the backup:
docker compose exec contracthub node dist/backup.js restore <backup-id> docker compose restart contracthub
Migrations by hand
If you want to run the database changes in a controlled way, set RUN_MIGRATIONS=false and run this before the update:
docker compose run --rm contracthub node dist/migrate.js
Cleaning up
docker image prune -a
deletes images that no container uses any more.
As of 2026-11-15 · Stuck? Write to us