Redeploy Overview

Container Redeploy

Container redeployment updates a Docker-based container to another image tag or software version while preserving the application data and selected configuration stored inside the existing container.

In this article

How Container Redeploy Works

Docker-based stacks are continuously updated with new versions, security fixes and product improvements. Redeployment allows the container image tag to be updated without rebuilding the environment or manually reinstalling the application.

New image preparationThe platform creates an internal container based on the selected target image tag.
Data identificationThe system identifies user data, volume content and supported configuration paths that must be preserved.
Container updateThe existing container is stopped and non-preserved system files are replaced with files from the selected image version.
Validation and recoveryThe operation is first applied to a snapshot and merged only when the redeployment succeeds.
i

Automatic return point

If the new configuration cannot be applied successfully, the platform discards the failed changes and returns the container to its previous state.

✓

Minimizing downtime

Redeploying a single node causes temporary service downtime. For a horizontally scaled layer, use sequential redeployment so the remaining nodes can continue processing incoming requests.

Before Starting

  • Review the release notes and compatibility requirements of the target image tag.
  • Back up important application and database data before a production update.
  • Confirm which files and directories are stored in persistent volumes.
  • Plan for brief downtime when redeploying a single-node service.
  • Update only one environment layer at a time.
!

Database downgrade limitation

Downgrading MySQL, MariaDB or Percona to a lower version through redeployment is not supported. When a downgrade is necessary, create a backup and restore the database after deploying the required version, preferably in a separate container.

Open the Redeploy Dialog

The redeployment interface can be opened directly from the dashboard or from the environment topology wizard.

1

Open redeployment from the dashboard

Locate the required node or container layer and click Redeploy Container(s). Selecting a layer starts the operation for all containers in that layer.

Redeploy container through topology wizard
Open the redeployment dialog from the image tag in the topology wizard.
2

Alternatively, use the topology wizard

Open Change Environment Topology and click the pencil icon beside the current image tag for the required layer.

Configure Redeploy Options

1

Select the target image tag

Choose the required version from the Tag list in the Redeploy Containers dialog.

Keep volumes dataProtects mounted-volume data from deletion and keeps it available after redeployment.
Simultaneous deploymentRedeploys all horizontally scaled nodes at the same time. It is faster but causes brief application downtime.
Sequential deployment with delayRedeploys nodes one by one with a defined delay so another active node can continue serving requests.
Temporarily remove nodes from DNSExcludes the node being updated from internal and external DNS records during sequential redeployment.
i

DNS update delay

Removing a node from DNS can add extra time because DNS records use a time-to-live value and cannot always be disabled immediately. Keeping it enabled minimizes the risk of requests being routed to a node during its update.

2

Start the redeployment

Review the selected tag and options, click Redeploy, and confirm the operation in the confirmation dialog.

Container redeployment logs
Review the node, tag change and duration in the redeployment logs.

Complete and Review the Operation

After the update completes, the platform displays a notification in the upper-right area of the dashboard.

Click Show Logs to review the updated node ID, previous tag, new tag and operation duration.

Container redeployment success notification
A dashboard notification confirms that container redeployment has completed.

Expected Result

The selected container or layer is updated to the chosen image tag. Preserved application data and mounted-volume content remain available, and the dashboard records the completed update in the operation logs.

Important Notes

  • Only one environment layer can be redeployed at a time.
  • Keep volume data enabled when application information is stored in mounted volumes.
  • Use sequential deployment for horizontally scaled production services when minimum downtime is required.
  • Simultaneous deployment is faster but briefly stops all nodes in the selected layer.
  • Do not use redeployment to downgrade MySQL, MariaDB or Percona databases.
  • Always review the operation logs after the update.

Common Issues and Solutions

Application data is missingConfirm that the required directories were stored in persistent volumes and that Keep Volumes Data was enabled.
Service was temporarily unavailableA single-node or simultaneous redeployment causes brief downtime. Use horizontally scaled nodes with sequential deployment.
Redeploy action is unavailableCheck whether another layer in the same environment is already being redeployed.
Requests reach an updating nodeEnable temporary DNS removal during sequential deployment and allow time for DNS TTL propagation.
New version fails to startReview the redeployment logs, image compatibility, required variables and application configuration. The platform should restore the previous state when the operation fails.

Related Guides