Running CDM

Updating

docker compose pull && docker compose up -d

CDM reads its configuration once at start. To apply a changed setting, recreate the container with docker compose up -d; a plain docker restart keeps the old values. With docker run, remove the container and run it again.

Backups

Back up the cdm-data volume, mounted at /data. It holds the cluster list, capacity history (the last 90 days), audit trail, muted findings, user preferences, sign-in sessions and settings, so CDM can be recreated from it at any time. Take the backup with the container stopped or from a volume snapshot, because a copy of the database taken while CDM writes to it can be inconsistent.

Cluster credentials inside it are encrypted with your CDM_SECRET_KEY, which therefore belongs in your backup too, stored separately. CDM cannot read the clusters in a backup without the key that encrypted them.

Logs

docker logs cdm
docker compose logs -f cdm

CDM writes its sign-in decisions here, which is what to read when someone lands on the wrong role. See Checking what CDM received.