- \n
- When you update, your custom data and important system files are kept safe.\n
- \n
- Your files are stored in volumes<\/a>, both default and custom ones.<\/li>\n
- Files listed in \/etc\/jelastic\/redeploy.conf (these are special settings needed for the containers to work)<\/li>\n
- Configurations related to AutoFS and NFS (\/etc\/autofs.jelastic, \/etc\/auto.master, \/etc\/exports)<\/li>\n
- Firewall settings (\/etc\/sysconfig\/iptables-custom, \/etc\/sysconfig\/iptables4-jelastic, \/etc\/sysconfig\/iptables6-jelastic, \/etc\/iptables\/rules.v4)<\/li>\n
- Access info for SSH (\/root\/.ssh\/authorized_keys, \/root\/.ssh\/authorized_keys2, \/root\/.ssh\/id_rsa)<\/li>\n<\/ul>\n<\/li>\n
- Your custom settings<\/a>, like commands and links, won’t change.<\/li>\n
- If you’re using multiple instances<\/a>, you can update them one by one without any downtime.<\/li>\n<\/ol>\n
This means you can update your Docker container to a new version without affecting your application. Using the platform, you can redeploy containers with just a few clicks on the dashboard<\/a> or automate it with the API<\/a>.<\/p>\n
Note:<\/strong> If you’re using MySQL, MariaDB, or Percona databases, you can’t go back to a lower version. If you need to, make sure to back up your database before redeploying or use a separate container for restoration.<\/div>\n<\/div>\n<\/div>\n\t\t\n\t\t\t\n \n \n\n\n \n \t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n<\/div>\nUpdate Container via Dashboard<\/h2>\n
The easiest way to update a template tag is by using the platform dashboard.<\/p>\n
The steps below will guide you through what you need to do.<\/p>\n
Step 1.<\/strong> You can access the redeployment options in two ways:<\/p>\n
Click the “Redeploy Container(s)<\/strong>” button next to the node or layer you want to update.<\/p>\n
![\"Redeploy](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Redeploy-Containers.png\" "\\"Redeploy")
<\/a><\/p>\nClick the pencil<\/strong> icon next to the layer tag version in the topology wizard if you’re changing the environment’s structure.<\/p>\n
![\"Change](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Pencil-icon.png\" "\\"Change")
<\/a><\/p>\nStep 2.<\/strong> This opens the redeployment window, where you can choose a new tag for your container(s).<\/p>\n
![\"Select](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Select-container-tag.png\" "\\"Select")
<\/a><\/p>\nYou also have some extra choices:<\/p>\n
- \n
- You can choose to keep your volume<\/a> data safe. If you turn this on, your data won’t be erased when you redeploy.<\/li>\n
- If you have containers that are scaled horizontally<\/a>, you can pick how they get updated:\n
- \n
- Simultaneous deployment updates all nodes together, which is faster but might briefly stop your application.<\/li>\n
- Sequential deployment with delay updates one node at a time, with a pause between each.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
This ensures that there’s always a node running to handle requests so that your application keeps running smoothly.<\/p>\n
Once you’ve set everything up, click “Redeploy<\/strong>” and confirm in the pop-up box.<\/p>\n
Step 3.<\/strong> When the update finishes, you’ll see a notification in the top right of the dashboard.<\/p>\n
![\"Completed](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Completed-redeployment-notification.png\" "\\"Completed")
<\/a><\/p>\nYou can click “Show Logs<\/strong>” to see details about the updated container, like its ID, name, tag, and how long it took to update.<\/p>\n
![\"Container](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Container-logs.png\" "\\"Container")
<\/a><\/p>\nThat’s it! Now you know how to update a container using the platform dashboard.<\/p>\n
<\/div>\n\t\t\n\t\t\t\n \n \n\n\n \n \t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n<\/div>\nUpdate Container via Platform API\/CS\/CLI<\/h2>\n
The update can be made automatic using platform API<\/a>, Cloud Scripting<\/a>, and CLI<\/a> (command-line interface).<\/p>\n
Important Note:<\/strong> You can find a detailed example of how to update containers using the CLI in the guide linked below.<\/div>\n<\/div>\nTo update containers, you use the environment.Control.RedeployContainers<\/a> method. It needs the following information:<\/p>\n
- \n
- envName:<\/strong> The name of the environment where you want to update containers.<\/li>\n
- session:<\/strong> Your user session or token<\/a> for authentication.<\/li>\n
- nodeGroup:<\/strong> The identifier for the layer in the environment you want to update (if needed).<\/li>\n
- nodeId:<\/strong> The ID number of the specific container you want to update (if needed).<\/li>\n
- tag:<\/strong> The version of the image you want to use for the update.<\/li>\n
- useExistingVolumes:<\/strong> Set it to true if you want to keep data in the mounted volumes when updating (optional).<\/li>\n
- login and password:<\/strong> Your credentials to access an image from a private registry (optional).<\/li>\n<\/ul>\n
![\"Redeploy](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Redeploy-Containers-tags.png\" "\\"Redeploy")
<\/a><\/p>\nYou must provide either nodeGroup or nodeId to define the target of the operation. The method will use nodeGroup if both are provided, but it will fail if neither is specified.<\/p>\n
You can use the following formats in your automation scripts<\/a> to define the update:<\/p>\n
1. To update a whole layer of containers:<\/p>\n
api:<\/strong> environment.control.RedeployContainers
\nnodeGroup:<\/strong> {nodeGroup}
\ntag:<\/strong> {myImage}:{newTag}<\/p>\nHere:<\/p>\n
{nodeGroup}:<\/strong> The layer (or node group) where all containers should be updated.
\n{myImage}:<\/strong> The name of the image to use.
\n{newTag}:<\/strong> The version of the image.<\/p>\n2. To update a specific container:<\/p>\n
api:<\/strong> environment.control.RedeployContainers
\nnodeId:<\/strong> {nodeId}
\ntag:<\/strong> {myImage}:{newTag}<\/p>\nHere, replace {nodeId} with the ID number of the container you want to update. The other placeholders are the same as in the previous example.<\/p>\n
\r\nhttps:\/\/app.cp-accuweb.cloud\/1.0\/environment\/control\/rest\/redeploycontainers?envName=accuweb-container&session=caf1288acfd3444e8d41a41e5ef5b923ca46ee79&tag=11.0.0-M18-openjdk-22-almalinux-9&nodeGroup=Application Servers&nodeId=4863&useExistingVolumes=true\r\n\r\nApi: https:\/\/app.cp-accuweb.cloud\/1.0\/environment\/control\/rest\/redeploycontainers?envName=accuweb-container\r\nSession: caf1288acfd3444e8d41a41e5ef5b923ca46ee79\r\nTag: 11.0.0-M18-openjdk-22-almalinux-9\r\nnodeGroup: Application Server\r\nNodeid: 4863\r\nuseExistingVolumes: true<\/code><\/pre>\nNote:<\/strong> You need to use an application like Postman<\/strong> to run the automatic script.<\/div>\n<\/div>\nOnce you execute the script from the application, the container will be redeployed, and you can see it on the AccuWeb Cloud dashboard.<\/p>\n
![\"Redeployed](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Container-Redeployed.png\" "\\"Redeployed")
<\/a><\/p>\nKeeping Your Own Data Safe When You Redeploy Your Container<\/strong><\/h2>\n
Every container<\/a> managed by the platform has a special file called redeploy.conf<\/strong> in the \/etc\/jelastic\/<\/strong> folder. This file holds important settings for your container. When you update your container, the platform makes sure these settings stay safe. You can find and manage this file easily using the built-in file manager<\/a>.<\/p>\n
![\"redeploy.conf\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/redeploy.conf_.png\" "\\"redeploy.conf\\"")
<\/a><\/p>\nThe redeploy.conf file has two parts: system<\/a> and custom<\/a>. You can use it to back up<\/a> important system files.<\/p>\n
System Files and Folders<\/h2>\n
Important Note:<\/strong> Only change the “system files and folders<\/strong>” list if you know exactly what you’re doing.<\/div>\n<\/div>\n![\"Change](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Change-system-files-and-folders-list.png\" "\\"Change")
<\/a><\/p>\nHere, you’ll find configurations that your container needs to update correctly. Some common files are the same on all setups:<\/p>\n
- \n
- \/etc\/jelastic\/redeploy.conf:<\/strong> This file tracks what needs to be saved when you update your container.<\/li>\n
- ${home}\/.bash_profile:<\/strong> It holds settings for the command line, like messages and configurations.<\/li>\n
- \/etc\/sysconfig\/iptables:<\/strong> This file has default rules for the firewall.<\/li>\n
- \/etc\/sysconfig\/iptables-custom:<\/strong> Here, you can put your own firewall rules<\/a>.<\/li>\n
- \/var\/lib\/jelastic\/keys:<\/strong> This is where your SSH keys<\/a> are stored for accessing the container and other containers.<\/li>\n<\/ul>\n
Each type of container might have different stack-specific files listed in its own redeploy.conf.<\/p>\n
Custom Files and Folders<\/h2>\n
Remember: Only include system setup files necessary for your container to work properly during updates. For other files, like your application’s data, use container volumes<\/a>.<\/p>\n
- ${home}\/.bash_profile:<\/strong> It holds settings for the command line, like messages and configurations.<\/li>\n
- session:<\/strong> Your user session or token<\/a> for authentication.<\/li>\n
- envName:<\/strong> The name of the environment where you want to update containers.<\/li>\n
- If you have containers that are scaled horizontally<\/a>, you can pick how they get updated:\n
- Your files are stored in volumes<\/a>, both default and custom ones.<\/li>\n
![\"Custom](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Custom-files-and-folders.png\" "\\"Custom")
<\/a><\/p>\n![\"Backup\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/05\/Backup.png\" "\\"Backup\\"")
<\/a><\/p>\n