Documentation

Update

Use dcimctl to update the installed runtime, dashboard and API safely from the host.
Updates are performed from the DCIM server with dcimctl. The command checks the installed license, downloads the signed release, verifies the artifacts and recreates the application services.
Plan updates during a maintenance window. The update restarts DCIM services and may run database migrations, so users should avoid changing inventory while the update is running.

Before updating

Create a fresh backup before running an update. DCIM updates do not create a hidden rollback backup; backups are controlled by the backup system. See Backups & restore if the backup target or retention still needs to be configured.
Check the current installation status and license state before starting:
Pre-update checks
dcimctl status
dcimctl license
The core services should be healthy before you update. If api, dash, db or proxy is already failing, fix that first or prepare a restore path.

Run the update

Sync the license first if the customer plan, limits or license state changed recently. Then run the update command:
Update commands
sudo dcimctl license --sync
sudo dcimctl update
If the installed version is already current, the command stops without replacing the runtime. If a new release is available, DCIM downloads the runtime and image artifacts to a temporary directory, verifies them, runs migrations and recreates the application services.

After updating

When the command finishes, verify that the installation is healthy again:
Post-update checks
dcimctl status
systemctl is-active dcim-license-sync.timer
dcimctl status should show the expected services running. The license sync timer should be active so future license certificate refreshes continue automatically.

If the update fails

If the update fails before replacing runtime files, the temporary download directory is removed and the existing installation should remain in place. If it fails after runtime changes, inspect service status and logs from the host:
Inspect failed update
dcimctl status
docker compose -f /opt/dcim/docker-compose.yml --project-directory /opt/dcim logs --tail=200 api dash proxy db
Use a full backup and dcimctl restore when the runtime, database or environment files are inconsistent. Do not use dcimctl reset for failed updates; reset is only for removing the local installation before a fresh install.

Update video