Not Enough Disk Space During Update

EasyDCIM and Remote Agent updates create a pre-update backup by default. Before creating the backup, easydcim-control checks available disk space.

If disk usage is too high, the update can stop with a disk space warning or error.

Why The Update Stops

The pre-update backup is blocked when disk usage is above 90% on the backup target path. In practice, keep at least 10% free disk space before running an update.

A warning may also be shown when disk usage is above 80%, because backup or update operations may fail if the disk fills up during the process.

Check Disk Usage

Run:

df -h

Also check which paths use the most space:

du -h --max-depth=1 /opt | sort -h
docker system df

Clean Old Backups

For EasyDCIM application backups:

sudo easydcim-control app backup clean --keep 3

For Remote Agent backups:

sudo easydcim-control agent backup clean --keep 3

You can lower the number if you intentionally want to keep fewer local backups.

Clean Docker Cache

If Docker images or build cache use too much space, review Docker usage first:

docker system df

Then remove unused Docker data only if you understand what will be deleted:

sudo docker system prune

Do not remove Docker volumes unless you are sure they do not contain required data.

Run The Update Again

After freeing disk space, run the update again:

sudo easydcim-control app update

or, for Remote Agent:

sudo easydcim-control agent update

About --skip-backup

Both update commands support skipping the pre-update backup, but this should only be used when you already have a verified external backup.

Examples:

sudo easydcim-control app update --skip-backup
sudo easydcim-control agent update --skip-backup

Skipping the backup is not recommended as the first solution. Freeing disk space and keeping the pre-update backup is safer.