Note: This document is based on Jelastic version 4.6.
Once you have your Docker template deployed and properly configured, you receive a fully functional and stable application. However, the majority of Dockerized applications and services are continuously developed, delivering new product versions (implemented within tags) from time to time. Thus, most likely eventually you’ll need to update your already running template.With Jelastic, this operation could be performed just in a few clicks, whilst providing the following benefits:
- data, stored within the mounted to a container volumes, is saved and will remain available afterwards through being packed into separate .tar.gz archives, which are automatically transferred out/in the container to the host physical server during this operation
- all the previously specified custom configurations (like run commands, links, variables, etc) won’t be affected
if operating with multiple template instances (i.e. in case it was scaled horizontally), the update can be performed implicitly and causing no downtime through redeploying the containers one by one
Update of the appropriate container with another tag version can be performed directly through the dashboard using GUI or remotely, with the help of Jelastic CLI client. So, let’s discover both of this options one-by-one.