Skip to Content
Last modified by Erik Bakker on 2025/04/18 13:54
From version 138.2
edited by Bas Elzinga
on 2024/12/17 12:19
Change comment: There is no comment for this version
To version 122.1
edited by Carlijn Kokkeler
on 2024/03/28 11:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.BasElzinga
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In eMagiz's current runtime architecture, Docker technology is utilized to deploy runtimes efficiently. eMagiz provides specific runtime images that can be deployed within dockerized environments. This section outlines the steps needed to prepare a Windows server for the installation of the eMagiz Deploy Agent, which is responsible for downloading these images from the eMagiz infrastructure.
2 +In this microlearning, we will focus on how an on-premises server can be prepared for a eMagiz Deploy agent installation.
3 3  
4 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -9,7 +9,7 @@
9 9  * Good understanding of eMagiz runtimes in general
10 10  
11 11  == 2. Key concepts ==
12 -In the current runtime architecture of eMagiz, Docker technology is used to deploy runtimes. eMagiz creates specific runtime images that contain the eMagiz runtime, and can be deployed in dockerized environments.
12 +In the new runtime architecture of eMagiz, Docker technology is used to deploy runtimes. eMagiz creates specific runtime images that contain the eMagiz runtime, and can be deployed in dockerized environments.
13 13  
14 14  In the below section the Windows variant is described in terms of how to prepare the server to allow the [[eMagiz Deploy Agent>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]] to be installed. That agent allows to download images from the eMagiz infrastructure.
15 15  
... ... @@ -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
... ... @@ -37,9 +37,6 @@
37 37   ** 3.74.190.88:8443
38 38   ** 35.158.46.28:8444
39 39   ** 3.74.190.88:8444
40 - ** 18.199.123.240
41 - ** 18.184.211.189
42 - ** 3.123.136.31
43 43  
44 44  * When using a cloudslot number **above** 125, the following configuration is needed to communicate to your JMS.
45 45   ** 3.74.209.20:443
... ... @@ -47,10 +47,7 @@
47 47   ** 3.74.209.20:8443
48 48   ** 3.76.127.155:8443
49 49   ** 3.74.209.20:8444
50 - ** 3.76.127.155:8444
51 - ** 18.199.123.240
52 - ** 18.184.211.189
53 - ** 3.123.136.31{{/warning}}
49 + ** 3.76.127.155:8444{{/warning}}
54 54  
55 55  ===3.2 Installation Windows===
56 56  Whenever Windows is selected as operating system, you need to have a Windows Server 2022 version. Older Windows servers are **not** supported.
... ... @@ -60,45 +60,15 @@
60 60  To install or update docker on your machine, execute the following commands in powershell with administrative rights:
61 61  
62 62  {{code language="cmd"}}
63 -Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Install-update-docker/install-update-docker.ps1" -o install-update-docker-ce.ps1
64 -.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
59 +Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/Windows-Containers/Main/helpful_tools/Install-DockerCE/install-docker-ce.ps1" -o install-docker-ce.ps1
60 +.\install-docker-ce.ps1
65 65  {{/code}}
66 66  
67 67  {{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"]].
68 68  {{/info}}
69 69  
70 -==== 3.2.2 Customization ====
66 +==== 3.2.2 Check installation ====
71 71  
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 -
74 -{{warning}}Be aware that the customization will only take effect once you have restarted the machine.{{/warning}}
75 -
76 -===== 3.2.2.1 IP address range =====
77 -
78 -Below you can find the code necessary to configure a different IP address range.
79 -
80 -{{code language="cmd"}}
81 -cd C:\ProgramData\Docker\config\daemon.json
82 -#Add following lines
83 -{"fixed-cidr": "<ip-address>"}
84 -{{/code}}
85 -
86 -===== 3.2.2.2 Data location =====
87 -
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 -
90 -{{code language="cmd"}}
91 -cd C:\ProgramData\Docker\config\daemon.json
92 -#Add following lines
93 -{
94 - "data-root": "d:\\docker"
95 -}
96 -{{/code}}
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 -==== 3.2.3 Check installation ====
101 -
102 102  After executing the commands above, the server will restart if required. After the restart, execute the following command
103 103  
104 104  {{code language="cmd"}}
... ... @@ -108,7 +108,7 @@
108 108  If the command returns that the command cannot be found, please run the following command again.
109 109  
110 110  {{code language="cmd"}}
111 -.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
77 +.\install-docker-ce.ps1
112 112  {{/code}}
113 113  
114 114  ==== 3.2.3 Verify docker functionality ====
... ... @@ -140,6 +140,27 @@
140 140  .\uninstall-docker-ce.ps1
141 141  {{/code}}
142 142  
109 +{{info}}
110 +By default the docker daemon configuration file is located in the docker data path at {{code language="cmd"}}C:\ProgramData\docker\config\daemon.json{{/code}}.
111 +To check the configuration options and compatible options with Windows you can check: [[Configure Docker in Windows>>https://learn.microsoft.com/en-us/virtualization/windowscontainers/manage-docker/configure-docker-daemon||target="blank"]].
112 +
113 +{{warning}}
114 +Ignore the Uninstall section as it is outdated (For Windows Server 2016), instead refer to the previous section to Uninstall docker
115 +{{/warning}}
116 +
117 +**Example usage of the Docker daemon file**: You maybe want the Docker daemon to keep images and containers in an alternate path (D:
118 +drive for example). To do so you can add the following attribute to the Docker daemon file:
119 +
120 +{{code language="cmd"}}
121 +{
122 + "data-root": "d:\\docker"
123 +}
124 +{{/code}}
125 +
126 +If not specified, the default is {{code language="cmd"}}c:\programdata\docker{{/code}}
127 +
128 +{{/info}}
129 +
143 143  == 4. Key takeaways ==
144 144  
145 145  * 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
... ... @@ -148,21 +148,6 @@
148 148  
149 149  == 5. Suggested Additional Readings ==
150 150  
151 -* [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
152 -** [[eMagiz Runtime Generation 3 (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]
153 -* [[Release Information (Menu)>>doc:Main.Release Information.WebHome||target="blank"]]
154 -** [[Environment Templates (Navigation)>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
155 -* [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
156 -** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]]
157 -*** [[Interpret on-premise logging (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-interpret-on-premise-logging.WebHome||target="blank"]]
158 -*** [[eMagiz Deploy agent (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]]
159 -* [[Advanced (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]]
160 -** [[Lifecycle Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Lifecycle Management.WebHome||target="blank"]]
161 -*** [[Impact of Runtime Image Upgrades (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Lifecycle Management.advanced-lifecycle-management-impact-of-runtime-image-upgrades.WebHome||target="blank"]]
162 -* [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]]
163 -** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]]
164 -*** [[Install Docker for Linux (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-linux-installguide.WebHome||target="blank"]]
165 -* [[Install Docker (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=install+docker||target="blank"]]
166 166  * Docker command line cheatsheet: [[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]]
167 167  
168 168  )))((({{toc/}}))){{/container}}{{/container}}