Skip to Content
Last modified by Erik Bakker on 2026/04/21 12:15
From version 151.1
edited by Erik Bakker
on 2026/04/21 12:15
Change comment: There is no comment for this version
To version 141.1
edited by Erik Bakker
on 2025/10/19 21:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,12 +17,8 @@
17 17  
18 18  ===3.1 General requirements===
19 19  
20 -{{info}}It is advised to use Docker version 29.1.3 as this is the version being used in the latest eMagiz cloud template. We advise aligning the on-premise Docker version and updating it according to the release notes of the [[Cloud templates>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]].
21 -{{/info}}
22 -
23 23  {{info}}
24 -* When **your** security requirements require **DNS Whitelisting**, the following DNS-level configuration is needed to communicate with our infrastructure and the specific eMagiz model(s) you need to connect to. These IP addresses are subject to periodic change on our end.
25 -
21 +* Standard configuration to ensure that communication between your server and eMagiz to ensure communication.
26 26   ** registry.emagiz.com:443
27 27   ** controlplane.emagiz.com:443
28 28   ** controlplane-agent.emagiz.com:443
... ... @@ -29,16 +29,11 @@
29 29   ** controltower.emagiz.com:443
30 30   ** controltower.kpn-dsh.com:443
31 31   ** controlbus.emagiz.com:443
32 - ** {yourcloudslotid}.emagizcloud.com:8443
33 -
34 -* Preferably we suggest to implement the following entries on DNS level.
35 - ** *.emagizcloud.com
36 - ** *.emagiz.com
37 - ** *.kpn-dsh.com{{/info}}
28 + ** Preferably the entry should be *.emagiz.com
29 + ** Preferably the entry should be *.kpn-dsh.com{{/info}}
38 38  
39 39  {{warning}}
40 -* When **your** security requirements require **IP Whitelisting**, the following IP-level configuration is needed to communicate with our infrastructure and the specific eMagiz model(s) you need to connect to. These IP addresses are subject to periodic change on our end.
41 -
32 +* When using **IP Whitelisting**, the following configuration is needed to communicate to your JMS.
42 42   ** 35.158.46.28:443
43 43   ** 3.74.190.88:443
44 44   ** 35.158.46.28:8443
... ... @@ -51,18 +51,16 @@
51 51   ** 3.76.127.155:8443
52 52   ** 3.74.209.20:8444
53 53   ** 3.76.127.155:8444
54 - ** 18.199.123.240:443
55 - ** 18.184.211.189:443
56 - ** 3.123.136.31:443
57 - ** 3.66.44.69:443
58 - ** 52.57.64.170:443
59 - ** 63.182.102.95:443{{/warning}}
45 + ** 18.199.123.240
46 + ** 18.184.211.189
47 + ** 3.123.136.31{{/warning}}
60 60  
61 61  ===3.2 Installation Windows===
62 -When Windows is selected as the operating system, you need Windows Server 2022. Older Windows servers are **not** supported.
50 +Whenever Windows is selected as operating system, you need to have a Windows Server 2022 version. Older Windows servers are **not** supported.
63 63  
52 +
64 64  ==== 3.2.1 Docker Installation ====
65 -To install Docker on your machine, execute the following commands in PowerShell with administrative rights:
54 +To install or update docker on your machine, execute the following commands in powershell with administrative rights:
66 66  
67 67  {{code language="cmd"}}
68 68  Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Install-update-docker/install-update-docker.ps1" -o install-update-docker-ce.ps1
... ... @@ -69,35 +69,38 @@
69 69  .\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
70 70  {{/code}}
71 71  
61 +{{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"]].
62 +{{/info}}
63 +
72 72  ==== 3.2.2 Customization ====
73 73  
74 -After installing Docker, you can stick with the standard configuration or adjust specific settings. Settings that can be of particular interest include the one that defines the IP address range your Docker installation will use to run containers, and the one 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"]].
66 +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"]].
75 75  
76 76  {{warning}}Be aware that the customization will only take effect once you have restarted the machine.{{/warning}}
77 77  
78 78  ===== 3.2.2.1 IP address range =====
79 79  
80 -Below is the code needed to configure a different IP address range.
72 +Below you can find the code necessary to configure a different IP address range.
81 81  
82 82  {{code language="cmd"}}
83 83  cd C:\ProgramData\Docker\config\daemon.json
84 -#Add the following lines
76 +#Add following lines
85 85  {"fixed-cidr": "<ip-address>"}
86 86  {{/code}}
87 87  
88 88  ===== 3.2.2.2 Data location =====
89 89  
90 -Below is an example of switching from the default C directory ({{code language="cmd"}}c:\programdata\docker{{/code}}) to the D directory to store Docker data. Based on your internal configuration, you can choose the best suitable variant if needed. To do so, you can add the following attribute to the Docker daemon file:
82 +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 91  
92 92  {{code language="cmd"}}
93 93  cd C:\ProgramData\Docker\config\daemon.json
94 -#Add the following lines
86 +#Add following lines
95 95  {
96 96   "data-root": "d:\\docker"
97 97  }
98 98  {{/code}}
99 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}}
92 +{{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}}
101 101  
102 102  ==== 3.2.3 Check installation ====
103 103  
... ... @@ -107,13 +107,13 @@
107 107  docker ps
108 108  {{/code}}
109 109  
110 -If the command returns "command not found," please run the following command again.
102 +If the command returns that the command cannot be found, please run the following command again.
111 111  
112 112  {{code language="cmd"}}
113 113  .\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
114 114  {{/code}}
115 115  
116 -==== 3.2.3 Verify Docker functionality ====
108 +==== 3.2.3 Verify docker functionality ====
117 117  
118 118  Execute the following command
119 119  
... ... @@ -127,27 +127,12 @@
127 127  
128 128  ==== 3.2.4 Install eMagiz Deploy Agent ====
129 129  
130 -Install the eMagiz Deploy agent as described in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]]
122 +Install the eMagiz Deploy agent as can be found in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]]
131 131  
132 -=== 3.3 Update Docker ===
133 -When you are advised to update your Docker version, you can verify whether you are on the correct Docker version by executing the following command in PowerShell with administrative rights:
124 +===3.3 Uninstall Docker===
125 +To uninstall docker from your machine, execute the following commands in powershell with administrative rights:
134 134  
135 135  {{code language="cmd"}}
136 -docker version
137 -{{/code}}
138 -
139 -When this returns a version **lower** than the advised version shown under the "General requirements" section, you can update Docker on your machine. To do so, execute the following command in PowerShell with administrative rights:
140 -
141 -{{code language="cmd"}}
142 -.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
143 -{{/code}}
144 -
145 -{{warning}}It may happen that, due to the update, your containers are no longer starting up. To resolve this, please restart the containers, which can be done via a deployment plan or the deploy architecture.{{/warning}}
146 -
147 -===3.4 Uninstall Docker===
148 -To uninstall Docker from your machine, execute the following commands in PowerShell with administrative rights:
149 -
150 -{{code language="cmd"}}
151 151  Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Uninstall-docker/uninstall-docker.ps1" -o uninstall-docker-ce.ps1
152 152  {{/code}}
153 153  
... ... @@ -159,9 +159,9 @@
159 159  
160 160  == 4. Key takeaways ==
161 161  
162 -* eMagiz uses runtime images to deploy the eMagiz runtime on Dockerized environments. The runtime image holds all the information and components required to run the runtime
139 +* eMagiz uses runtime images to deploy emagiz runtime on dockerized environments. The runtime image holds all the information and components required to run the runtime
163 163  * eMagiz has a specific agent that manages the download of that image to the on-premises server
164 -* The firewall of the on-premises environment should allow outgoing traffic without any restrictions. If that is not desirable, eMagiz can provide the addresses and ports needed to set up the appropriate firewall rules.
141 +* The firewall of the on-premises environment should allow outgoing traffic without any restriction. In case that is not desirable, eMagiz can provide the addresses and ports needed to setup the right firewall rules.
165 165  
166 166  == 5. Suggested Additional Readings ==
167 167