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 38.1
edited by Erik Bakker
on 2026/02/10 10:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R19 Docker - Single Lane
1 +R18 Docker - Single Lane
Content
... ... @@ -1,13 +1,17 @@
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** final template to use the **R18** single lane release. This upgrade is service-affecting, as all instances have to be recreated.
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 **R18** 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 +* Security improvements to the eMagiz infrastructure
8 +* Update Ubuntu version
9 +* Update Docker version
10 +* Update control agent version
11 +* Update Authorization Server (if applicable)
8 8  
9 9  **Update Steps**
10 -* Use the final **R19** template (service affecting) (duration: 15 minutes)
14 +* Use the final **R18** template (service affecting) (duration: 15 minutes)
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,4 +14,4 @@
14 14  ** Check if messages pass through the model by verifying a critical message flow in external systems.
15 15  
16 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.
21 +In case your model running fully on-premise you need to upgrade your agents by upgrading to the next available template (R3).