Skip to Content
Last modified by Erik Bakker on 2026/01/23 13:45
From version 135.1
edited by Erik Bakker
on 2024/11/29 08:30
Change comment: There is no comment for this version
To version 142.1
edited by Erik Bakker
on 2026/01/23 12:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,22 +17,22 @@
17 17  
18 18  ===3.1 General requirements===
19 19  
20 +{{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 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 +
20 20  {{info}}
21 21  * Standard configuration to ensure that communication between your server and eMagiz to ensure communication.
22 22   ** registry.emagiz.com:443
23 - ** controlplane.emagiz.com:8000
26 + ** controlplane.emagiz.com:443
27 + ** controlplane-agent.emagiz.com:443
28 + ** controltower.emagiz.com:443
24 24   ** controltower.kpn-dsh.com:443
30 + ** controlbus.emagiz.com:443
25 25   ** Preferably the entry should be *.emagiz.com
26 26   ** Preferably the entry should be *.kpn-dsh.com{{/info}}
27 27  
28 28  {{warning}}
29 -* In case of a very strict firewall configuration, additional configuration is needed to communicate to the eMagiz infrastructure.
30 - ** controltower.emagiz.com:443
31 - ** controltower.kpn-dsh.com:443
32 - ** controlbus.emagiz.com:443
33 - ** controlplane.emagiz.com:443
34 -
35 -* When using cloudslot number **equal to or below** 125, the following configuration is needed to communicate to your JMS.
35 +* When using **IP Whitelisting**, the following configuration is needed to communicate to your JMS.
36 36   ** 35.158.46.28:443
37 37   ** 3.74.190.88:443
38 38   ** 35.158.46.28:8443
... ... @@ -39,11 +39,6 @@
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
45 -
46 -* When using a cloudslot number **above** 125, the following configuration is needed to communicate to your JMS.
47 47   ** 3.74.209.20:443
48 48   ** 3.76.127.155:443
49 49   ** 3.74.209.20:8443
... ... @@ -54,12 +54,13 @@
54 54   ** 18.184.211.189
55 55   ** 3.123.136.31{{/warning}}
56 56  
57 -===3.2 Installation Windows===
58 -Whenever Windows is selected as operating system, you need to have a Windows Server 2022 version. Older Windows servers are **not** supported.
59 59  
60 60  
54 +===3.2 Installation Windows===
55 +When Windows is selected as the operating system, you need Windows Server 2022. Older Windows servers are **not** supported.
56 +
61 61  ==== 3.2.1 Docker Installation ====
62 -To install or update docker on your machine, execute the following commands in powershell with administrative rights:
58 +To install 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,41 +66,36 @@
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 -
72 72  ==== 3.2.2 Customization ====
73 73  
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}}
67 +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"]].
77 77  
69 +{{warning}}Be aware that the customization will only take effect once you have restarted the machine.{{/warning}}
70 +
78 78  ===== 3.2.2.1 IP address range =====
79 79  
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
73 +Below is the code needed to configure a different IP address range.
87 87  
88 88  {{code language="cmd"}}
89 -sudo nano /etc/docker/daemon.json
90 -#Add following lines
91 -{"bip": "<ip-address>"}
76 +cd C:\ProgramData\Docker\config\daemon.json
77 +#Add the following lines
78 +{"fixed-cidr": "<ip-address>"}
92 92  {{/code}}
93 -
80 +
94 94  ===== 3.2.2.2 Data location =====
95 95  
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:
83 +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:
97 97  
98 98  {{code language="cmd"}}
86 +cd C:\ProgramData\Docker\config\daemon.json
87 +#Add the following lines
99 99  {
100 100   "data-root": "d:\\docker"
101 101  }
102 102  {{/code}}
103 103  
93 +{{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}}
94 +
104 104  ==== 3.2.3 Check installation ====
105 105  
106 106  After executing the commands above, the server will restart if required. After the restart, execute the following command
... ... @@ -109,13 +109,13 @@
109 109  docker ps
110 110  {{/code}}
111 111  
112 -If the command returns that the command cannot be found, please run the following command again.
103 +If the command returns "command not found," please run the following command again.
113 113  
114 114  {{code language="cmd"}}
115 115  .\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
116 116  {{/code}}
117 117  
118 -==== 3.2.3 Verify docker functionality ====
109 +==== 3.2.3 Verify Docker functionality ====
119 119  
120 120  Execute the following command
121 121  
... ... @@ -129,12 +129,25 @@
129 129  
130 130  ==== 3.2.4 Install eMagiz Deploy Agent ====
131 131  
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"]]
123 +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"]]
133 133  
134 -===3.3 Uninstall Docker===
135 -To uninstall docker from your machine, execute the following commands in powershell with administrative rights:
125 +==== 3.3 Update Docker ====
126 +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:
136 136  
137 137  {{code language="cmd"}}
129 +docker version
130 +{{/code}}
131 +
132 +When this returns a version **lower** than the advised version shown below, you can update Docker on your machine. To do so, execute the following command in PowerShell with administrative rights:
133 +
134 +{{code language="cmd"}}
135 +.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
136 +{{/code}}
137 +
138 +===3.4 Uninstall Docker===
139 +To uninstall Docker from your machine, execute the following commands in PowerShell with administrative rights:
140 +
141 +{{code language="cmd"}}
138 138  Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Uninstall-docker/uninstall-docker.ps1" -o uninstall-docker-ce.ps1
139 139  {{/code}}
140 140  
... ... @@ -146,9 +146,9 @@
146 146  
147 147  == 4. Key takeaways ==
148 148  
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
153 +* 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
150 150  * eMagiz has a specific agent that manages the download of that image to the on-premises server
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.
155 +* 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.
152 152  
153 153  == 5. Suggested Additional Readings ==
154 154