Skip to Content
Last modified by Erik Bakker on 2025/04/18 13:54
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 138.2
edited by Bas Elzinga
on 2024/12/17 12:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.BasElzinga
Content
... ... @@ -20,18 +20,16 @@
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:443
23 23   ** controlplane.emagiz.com:8000
25 + ** controlplane-agent.emagiz.com:8000
26 + ** controltower.emagiz.com:443
24 24   ** controltower.kpn-dsh.com:443
28 + ** 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 35  * When using cloudslot number **equal to or below** 125, the following configuration is needed to communicate to your JMS.
36 36   ** 35.158.46.28:443
37 37   ** 3.74.190.88:443
... ... @@ -68,39 +68,37 @@
68 68  
69 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 70  {{/info}}
71 -
69 +
72 72  ==== 3.2.2 Customization ====
73 73  
74 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}}
77 77  
74 +{{warning}}Be aware that the customization will only take effect once you have restarted the machine.{{/warning}}
75 +
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
78 +Below you can find the code necessary to configure a different IP address range.
87 87  
88 88  {{code language="cmd"}}
89 -sudo nano /etc/docker/daemon.json
81 +cd C:\ProgramData\Docker\config\daemon.json
90 90  #Add following lines
91 -{"bip": "<ip-address>"}
83 +{"fixed-cidr": "<ip-address>"}
92 92  {{/code}}
93 -
85 +
94 94  ===== 3.2.2.2 Data location =====
95 95  
96 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:
97 97  
98 98  {{code language="cmd"}}
91 +cd C:\ProgramData\Docker\config\daemon.json
92 +#Add following lines
99 99  {
100 100   "data-root": "d:\\docker"
101 101  }
102 102  {{/code}}
103 103  
98 +{{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}}
99 +
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