Skip to Content
Last modified by Erik Bakker on 2025/04/18 13:54
From version 132.1
edited by Carlijn Kokkeler
on 2024/09/03 12:20
Change comment: There is no comment for this version
To version 137.1
edited by Erik Bakker
on 2024/11/29 08:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In eMagiz's new runtime architecture, Docker technology is utilized to deploy runtimes efficiently. eMagiz provides specific runtime images that can be deployed within dockerized environments. This section outlines the steps needed to prepare a Windows server for the installation of the eMagiz Deploy Agent, which is responsible for downloading these images from the eMagiz infrastructure.
2 +In eMagiz's current runtime architecture, Docker technology is utilized to deploy runtimes efficiently. eMagiz provides specific runtime images that can be deployed within dockerized environments. This section outlines the steps needed to prepare a Windows server for the installation of the eMagiz Deploy Agent, which is responsible for downloading these images from the eMagiz infrastructure.
3 3  
4 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -9,7 +9,7 @@
9 9  * Good understanding of eMagiz runtimes in general
10 10  
11 11  == 2. Key concepts ==
12 -In the new runtime architecture of eMagiz, Docker technology is used to deploy runtimes. eMagiz creates specific runtime images that contain the eMagiz runtime, and can be deployed in dockerized environments.
12 +In the current runtime architecture of eMagiz, Docker technology is used to deploy runtimes. eMagiz creates specific runtime images that contain the eMagiz runtime, and can be deployed in dockerized environments.
13 13  
14 14  In the below section the Windows variant is described in terms of how to prepare the server to allow the [[eMagiz Deploy Agent>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]] to be installed. That agent allows to download images from the eMagiz infrastructure.
15 15  
... ... @@ -39,6 +39,9 @@
39 39   ** 3.74.190.88:8443
40 40   ** 35.158.46.28:8444
41 41   ** 3.74.190.88:8444
42 + ** 18.199.123.240
43 + ** 18.184.211.189
44 + ** 3.123.136.31
42 42  
43 43  * When using a cloudslot number **above** 125, the following configuration is needed to communicate to your JMS.
44 44   ** 3.74.209.20:443
... ... @@ -46,7 +46,10 @@
46 46   ** 3.74.209.20:8443
47 47   ** 3.76.127.155:8443
48 48   ** 3.74.209.20:8444
49 - ** 3.76.127.155:8444{{/warning}}
52 + ** 3.76.127.155:8444
53 + ** 18.199.123.240
54 + ** 18.184.211.189
55 + ** 3.123.136.31{{/warning}}
50 50  
51 51  ===3.2 Installation Windows===
52 52  Whenever Windows is selected as operating system, you need to have a Windows Server 2022 version. Older Windows servers are **not** supported.
... ... @@ -63,25 +63,38 @@
63 63  {{info}}It is advised to use Docker version 24.0.7 as this is the version being used in the latest eMagiz cloud template. We advise to align the on-premise Docker version and update it according to the release notes of the [[Cloud templates>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]].
64 64  {{/info}}
65 65  
66 -{{info}}
67 -By default the docker daemon configuration file is located in the docker data path at {{code language="cmd"}}C:\ProgramData\docker\config\daemon.json{{/code}}.
68 -To check the configuration options and compatible options with Windows you can check: [[Configure Docker in Windows>>https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-docker/configure-docker-daemon||target="blank"]].
72 +==== 3.2.2 Customization ====
69 69  
70 -**Example usage of the Docker daemon file**: You maybe want the Docker daemon to keep images and containers in an alternate path (D:
71 -drive for example). To do so you can add the following attribute to the Docker daemon file:
74 +After installing Docker you have the option to stick with the standard configuration of Docker or you can opt to alter some specific settings. Settings that can be of particular interest are the setting that defines the IP address range your Docker installation will use to run the containers and the setting that defines where to store data (i.e. containers and images). To check the full list of compatible configuration options for Windows you can check: [[Configure Docker in Windows>>https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-docker/configure-docker-daemon||target="blank"]].
72 72  
76 +{{warning}}Be aware that the customization will only take effect once you have restarted the machine.{{/warning}}
77 +
78 +===== 3.2.2.1 IP address range =====
79 +
80 +Below you can find the code necessary to configure a different IP address range.
81 +
73 73  {{code language="cmd"}}
83 +cd C:\ProgramData\Docker\config\daemon.json
84 +#Add following lines
85 +{"fixed-cidr": "<ip-address>"}
86 +{{/code}}
87 +
88 +===== 3.2.2.2 Data location =====
89 +
90 +Below you can find an example of switching from the default C directory ({{code language="cmd"}}c:\programdata\docker{{/code}}) to the D directory to store data related to Docker. Based on your internal configuration you can choose the best suitable variant if that is needed. To do so you can add the following attribute to the Docker daemon file:
91 +
92 +{{code language="cmd"}}
93 +cd C:\ProgramData\Docker\config\daemon.json
94 +#Add following lines
74 74  {
75 75   "data-root": "d:\\docker"
76 76  }
77 77  {{/code}}
99 +
100 +{{warning}}Note that when you want to create multiple customizations to your configuration the result in the daemon.json file should be a **valid** JSON structure{{/warning}}
78 78  
79 -If not specified, the default is {{code language="cmd"}}c:\programdata\docker{{/code}}.
102 +==== 3.2.3 Check installation ====
80 80  
81 -{{/info}}
82 -
83 -==== 3.2.2 Check installation ====
84 -
85 85  After executing the commands above, the server will restart if required. After the restart, execute the following command
86 86  
87 87  {{code language="cmd"}}
... ... @@ -131,8 +131,8 @@
131 131  
132 132  == 5. Suggested Additional Readings ==
133 133  
134 -** [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
135 -*** [[eMagiz Runtime Generation 3 (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]
153 +* [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
154 +** [[eMagiz Runtime Generation 3 (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]
136 136  * [[Release Information (Menu)>>doc:Main.Release Information.WebHome||target="blank"]]
137 137  ** [[Environment Templates (Navigation)>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
138 138  * [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]