Skip to main content
Choose your upgrade path first. For v6 targets, use the one-click runbook. For 4.x/5.x targets, use the historical procedure; today’s updater may require v6 services.

What it preserves

The updater keeps your customized Compose file, environment, SMTP, storage and credentials except for specific migrations implemented by that script. It does not add missing services or merge a new stack. Pulling an image does not update a pinned dependency tag.
  • Merge the target’s required services, configuration and model files before updating.
  • Keep existing MinIO/S3 data and proxy routing; moving to RustFS is a separate storage migration.
  • Retain database passwords, ENCRYPTION_KEY, auth secrets and Hub/Cube credentials.
  • Pin app, migration and dependency images. Download the updater from the same selected release tag.
See Prepare the target configuration.

Targeted changes by release

For Cube, a latest app tag resolves models from stable; a digest or custom tag may prevent automatic refresh. Use the manual model refresh with the app’s source release. Failed downloads leave old files in place, so inspect the result before accepting analytics. The port migration preserves an explicit address you chose and does not rewrite configurations selected through COMPOSE_FILE. If rendering/validation fails, it restores the edited files and continues with the old binding. Verify the resolved ports rather than assuming they changed. See port-binding details, including Docker Engine versions with loopback isolation limitations. Other installer behavior, such as IPv6 network setup, depends on the script version. Review the script you selected; do not attribute today’s behavior to every old release.

Recovery

Keep the saved configuration and model files until acceptance. An image-only rollback is not a general recovery plan for database, Hub or storage changes. Use the target’s release notes and coordinated restore; never delete the data volumes.