Skip to Content

Changes for page R19 Docker - Single Lane

Last modified by Erik Bakker on 2026/03/22 21:42
From version 40.1
edited by Erik Bakker
on 2026/03/22 21:42
Change comment: There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2023/06/06 08:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R19 Docker - Single Lane
1 +R8 - Docker Single lane
Content
... ... @@ -1,17 +1,21 @@
1 -**Service affecting** final template to use the **R19** single lane release. This upgrade is service-affecting, as all instances have to be recreated.
1 +Service affecting R8 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
2 2  
3 3  **Process**
4 -We upgrade in one step to use the new **R19** release of the cloud template. This step is service affecting.
4 +We upgrade in one step to use the new R8 release of the cloud template. This step is service affecting.
5 5  
6 6  **Overview**
7 -* Remove need for recycling underlying instance when adding containers to machine
7 +It improves the ease with which Static IP Addresses can be gathered and distributed by a user while at the same thing improving the security by upgrading the Ubuntu version.
8 8  
9 +**Updates**
10 +* Ability to fetch Static IP Addresses
11 +* New Ubuntu version with new security patches.
12 +
9 9  **Update Steps**
10 -* Use the final **R19** template (service affecting) (duration: 15 minutes)
14 +* Use the final template (service affecting) (duration: 10 minutes)
15 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
16 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
11 11  * User actions after applying the final template:
12 12  ** Check if all runtimes are reachable by Deploy Architecture.
13 13  ** Check if all flows have been installed according to the active release.
14 14  ** Check if messages pass through the model by verifying a critical message flow in external systems.
15 15  
16 -**Remarks**
17 -Adding/moving/deleting containers from machines will now not replace the underlying instances. This was only the case for singlelanes. Doublelanes do not have this behaviour and are not affected.