Container Tier Rolling Updates


When you deploy an application with at least one container-based tier, and the deployment is in the deployed state, the Update on-demand action becomes available for that deployment. This action is visible from the the Action dropdown field in the the Deployments List page and in the deployment's Deployment Details page.


The rolling update action is only available from the Deployments list page, not the Deployment details or Job details page.

Update Process

When you select this action you are presented with a dialog box enumerating all of the container images in your deployment. The following screenshot shows an example dialog box with two container images.

Enter the version tag for the version to update for all container images in the dialog box and click Update. If you leave the version tag field blank, the container will be updated to the latest version of the image stored in the Docker registry you are using.

This is a live update. Your existing replica sets continues to receive traffic until the replica sets with the new images are fully functional. Once that happens, traffic is redirected to the new replica sets. During the process, the status of your deployment changes to Updating until the update is complete, at which point the deployment status returns to deployed.

Workload Manager does not do a validity check for your version tag before attempting to perform the update procedure. If you enter a version tag that does not exist in the Docker registry you are referring to (either Docker Hub or your own private Docker registry). Even if the update action fails, the Container deployments continue to be restored with the previous image – before the rolling update action is initiated.


If you see the Unable to update container images on Deployment Details page error, go to Deployments list page and select Update from the actions dropdown menu.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks