Skip to Content
Last modified by Erik Bakker on 2025/04/18 13:54
From version 139.1
edited by Bas Elzinga
on 2024/12/17 12:20
Change comment: There is no comment for this version
To version 136.1
edited by Erik Bakker
on 2024/11/29 08:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.BasElzinga
1 +XWiki.ebakker
Content
... ... @@ -20,16 +20,18 @@
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
24 24   ** controlplane.emagiz.com:8000
25 - ** controlplane-agent.emagiz.com:8000
26 - ** controltower.emagiz.com:443
27 27   ** controltower.kpn-dsh.com:443
28 - ** controlbus.emagiz.com:443
29 29   ** Preferably the entry should be *.emagiz.com
30 30   ** Preferably the entry should be *.kpn-dsh.com{{/info}}
31 31  
32 32  {{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 +
33 33  * When using cloudslot number **equal to or below** 125, the following configuration is needed to communicate to your JMS.
34 34   ** 35.158.46.28:443
35 35   ** 3.74.190.88:443
... ... @@ -71,32 +71,34 @@
71 71  
72 72  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"]].
73 73  
74 -{{warning}}Be aware that the customization will only take effect once you have restarted the machine.{{/warning}}
76 +{{warning}}Be aware that the customization will only take effect once you have restarted Docker.{{/warning}}
75 75  
76 76  ===== 3.2.2.1 IP address range =====
77 77  
78 -Below you can find the code necessary 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
79 79  
80 80  {{code language="cmd"}}
81 -cd C:\ProgramData\Docker\config\daemon.json
89 +sudo nano /etc/docker/daemon.json
82 82  #Add following lines
83 -{"fixed-cidr": "<ip-address>"}
91 +{"bip": "<ip-address>"}
84 84  {{/code}}
85 -
93 +
86 86  ===== 3.2.2.2 Data location =====
87 87  
88 88  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:
89 89  
90 90  {{code language="cmd"}}
91 -cd C:\ProgramData\Docker\config\daemon.json
92 -#Add following lines
93 93  {
94 94   "data-root": "d:\\docker"
95 95  }
96 96  {{/code}}
97 97  
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 -
100 100  ==== 3.2.3 Check installation ====
101 101  
102 102  After executing the commands above, the server will restart if required. After the restart, execute the following command