ConsolePrepare a backup
Read the changelog and image release information. Record the current image digest, Compose configuration and environment. Back up both persistent volumes consistently before an update; make sure the recovery set has been tested.
Update the container
From the installation's Compose directory, run docker compose -f docker-compose.prod.yml up -d --pull always --wait. This uses the image reference configured in the bundle. If your organization pins a release, use its reviewed image/digest under your change policy. Keep the existing project identity and persistent volumes.
Verify the installation
Verify container health, administrator sign-in, host visibility and the protocols you use. Test an authorized SSH/SFTP or graphical connection and Docker access where configured. A green container alone does not prove remote connectivity.
Restore if needed
If the candidate fails, use the recorded image and, when a data migration requires it, the corresponding database and Vault recovery set. Do not point an old image at migrated data without checking compatibility. Keep a maintenance window available until the checks pass.