Skip to Content
Last modified by Erik Bakker on 2026/04/21 12:15
From version 148.1
edited by Erik Bakker
on 2026/04/21 11:58
Change comment: There is no comment for this version
To version 135.1
edited by Erik Bakker
on 2024/11/29 08:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,26 +17,22 @@
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 24  * Standard configuration to ensure that communication between your server and eMagiz to ensure communication.
25 25   ** registry.emagiz.com:443
26 - ** controlplane.emagiz.com:443
27 - ** controlplane-agent.emagiz.com:443
23 + ** controlplane.emagiz.com:8000
24 + ** controltower.kpn-dsh.com:443
25 + ** Preferably the entry should be *.emagiz.com
26 + ** Preferably the entry should be *.kpn-dsh.com{{/info}}
27 +
28 +{{warning}}
29 +* In case of a very strict firewall configuration, additional configuration is needed to communicate to the eMagiz infrastructure.
28 28   ** controltower.emagiz.com:443
29 29   ** controltower.kpn-dsh.com:443
30 30   ** controlbus.emagiz.com:443
31 - ** {yourcloudslotid}.emagizcloud.com:8443
32 -
33 -* Preferably we suggest to implement the following entries on DNS level.
34 - ** *.emagizcloud.com
35 - ** *.emagiz.com
36 - ** *.kpn-dsh.com{{/info}}
33 + ** controlplane.emagiz.com:443
37 37  
38 -{{warning}}
39 -* When using **IP Whitelisting**, the following configuration is needed to communicate to your JMS.
35 +* When using cloudslot number **equal to or below** 125, the following configuration is needed to communicate to your JMS.
40 40   ** 35.158.46.28:443
41 41   ** 3.74.190.88:443
42 42   ** 35.158.46.28:8443
... ... @@ -43,6 +43,11 @@
43 43   ** 3.74.190.88:8443
44 44   ** 35.158.46.28:8444
45 45   ** 3.74.190.88:8444
42 + ** 18.199.123.240
43 + ** 18.184.211.189
44 + ** 3.123.136.31
45 +
46 +* When using a cloudslot number **above** 125, the following configuration is needed to communicate to your JMS.
46 46   ** 3.74.209.20:443
47 47   ** 3.76.127.155:443
48 48   ** 3.74.209.20:8443
... ... @@ -53,13 +53,12 @@
53 53   ** 18.184.211.189
54 54   ** 3.123.136.31{{/warning}}
55 55  
56 -
57 -
58 58  ===3.2 Installation Windows===
59 -When Windows is selected as the operating system, you need Windows Server 2022. Older Windows servers are **not** supported.
58 +Whenever Windows is selected as operating system, you need to have a Windows Server 2022 version. Older Windows servers are **not** supported.
60 60  
60 +
61 61  ==== 3.2.1 Docker Installation ====
62 -To install Docker on your machine, execute the following commands in PowerShell with administrative rights:
62 +To install or update docker on your machine, execute the following commands in powershell with administrative rights:
63 63  
64 64  {{code language="cmd"}}
65 65  Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Install-update-docker/install-update-docker.ps1" -o install-update-docker-ce.ps1
... ... @@ -66,36 +66,41 @@
66 66  .\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
67 67  {{/code}}
68 68  
69 +{{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"]].
70 +{{/info}}
71 +
69 69  ==== 3.2.2 Customization ====
70 70  
71 -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"]].
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"]].
75 +
76 +{{warning}}Be aware that the customization will only take effect once you have restarted Docker.{{/warning}}
72 72  
73 -{{warning}}Be aware that the customization will only take effect once you have restarted the machine.{{/warning}}
74 -
75 75  ===== 3.2.2.1 IP address range =====
76 76  
77 -Below is the code needed to configure a different IP address range.
80 +Below you can find the recommended values depending on the range which can be filled in the value <ip-address> below:
81 +* 10.0.0.1/8
82 +** advised value 10.25.0.1/16
83 +* 172.16.0.1/12
84 +** advised value 172.16.0.1/16
85 +* 192.168.0.1/16
86 +** advised value 192.168.0.1/16
78 78  
79 79  {{code language="cmd"}}
80 -cd C:\ProgramData\Docker\config\daemon.json
81 -#Add the following lines
82 -{"fixed-cidr": "<ip-address>"}
89 +sudo nano /etc/docker/daemon.json
90 +#Add following lines
91 +{"bip": "<ip-address>"}
83 83  {{/code}}
84 -
93 +
85 85  ===== 3.2.2.2 Data location =====
86 86  
87 -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:
96 +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:
88 88  
89 89  {{code language="cmd"}}
90 -cd C:\ProgramData\Docker\config\daemon.json
91 -#Add the following lines
92 92  {
93 93   "data-root": "d:\\docker"
94 94  }
95 95  {{/code}}
96 96  
97 -{{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}}
98 -
99 99  ==== 3.2.3 Check installation ====
100 100  
101 101  After executing the commands above, the server will restart if required. After the restart, execute the following command
... ... @@ -104,13 +104,13 @@
104 104  docker ps
105 105  {{/code}}
106 106  
107 -If the command returns "command not found," please run the following command again.
112 +If the command returns that the command cannot be found, please run the following command again.
108 108  
109 109  {{code language="cmd"}}
110 110  .\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
111 111  {{/code}}
112 112  
113 -==== 3.2.3 Verify Docker functionality ====
118 +==== 3.2.3 Verify docker functionality ====
114 114  
115 115  Execute the following command
116 116  
... ... @@ -124,27 +124,12 @@
124 124  
125 125  ==== 3.2.4 Install eMagiz Deploy Agent ====
126 126  
127 -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"]]
132 +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"]]
128 128  
129 -=== 3.3 Update Docker ===
130 -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:
134 +===3.3 Uninstall Docker===
135 +To uninstall docker from your machine, execute the following commands in powershell with administrative rights:
131 131  
132 132  {{code language="cmd"}}
133 -docker version
134 -{{/code}}
135 -
136 -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:
137 -
138 -{{code language="cmd"}}
139 -.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
140 -{{/code}}
141 -
142 -{{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}}
143 -
144 -===3.4 Uninstall Docker===
145 -To uninstall Docker from your machine, execute the following commands in PowerShell with administrative rights:
146 -
147 -{{code language="cmd"}}
148 148  Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Uninstall-docker/uninstall-docker.ps1" -o uninstall-docker-ce.ps1
149 149  {{/code}}
150 150  
... ... @@ -156,9 +156,9 @@
156 156  
157 157  == 4. Key takeaways ==
158 158  
159 -* 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
149 +* 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
160 160  * eMagiz has a specific agent that manages the download of that image to the on-premises server
161 -* 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.
151 +* 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.
162 162  
163 163  == 5. Suggested Additional Readings ==
164 164