Changes for page Install Docker for Windows

Last modified by Erik Bakker on 2026/04/21 12:15

From 120.1 to 119.1

From version 151.1

edited by Erik Bakker
on 2026/04/21 12:15

Change comment: There is no comment for this version

To version 120.1

edited by CarlijnKokkeler
on 2024/03/28 11:00

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.ebakker
++XWiki.CarlijnKokkeler

Content

@@ -1,5 +1,5 @@
  {{container}}{{container layoutStyle="columns"}}(((
--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.
++In this microlearning, we will focus on how an on-premises server can be prepared for a eMagiz Deploy agent installation.
  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
@@ -9,7 +9,7 @@
  * Good understanding of eMagiz runtimes in general
  == 2. Key concepts ==
--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.
++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.
  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.
@@ -17,28 +17,22 @@
  ===3.1 General requirements===
--{{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"]].
--{{/info}}
--
  {{info}}
--* When **your** security requirements require **DNS Whitelisting**, the following DNS-level configuration is needed to communicate with our infrastructure and the specific eMagiz model(s) you need to connect to. These IP addresses are subject to periodic change on our end.
--
++* Standard configuration to ensure that communication between your server and eMagiz to ensure communication.
      ** registry.emagiz.com:443
--    ** controlplane.emagiz.com:443
--    ** controlplane-agent.emagiz.com:443
++    ** controlplane.emagiz.com:8000
++    ** controltower.kpn-dsh.com:443
++    ** Preferably the entry should be *.emagiz.com
++    ** Preferably the entry should be *.kpn-dsh.com{{/info}}
++
++{{warning}}
++* In case of a very strict firewall configuration, additional configuration is needed to communicate to the eMagiz infrastructure.
      ** controltower.emagiz.com:443
      ** controltower.kpn-dsh.com:443
      ** controlbus.emagiz.com:443
--    ** {yourcloudslotid}.emagizcloud.com:8443
--
--* Preferably we suggest to implement the following entries on DNS level.
--    ** *.emagizcloud.com
--    ** *.emagiz.com
--    ** *.kpn-dsh.com{{/info}}
++    ** controlplane.emagiz.com:443
--{{warning}}
--* When **your** security requirements require **IP Whitelisting**, the following IP-level configuration is needed to communicate with our infrastructure and the specific eMagiz model(s) you need to connect to. These IP addresses are subject to periodic change on our end.
--
++* When using cloudslot number **equal to or below** 125, the following configuration is needed to communicate to your JMS.
      ** 35.158.46.28:443
      ** 3.74.190.88:443
      ** 35.158.46.28:8443
@@ -45,62 +45,29 @@
      ** 3.74.190.88:8443
      ** 35.158.46.28:8444
      ** 3.74.190.88:8444
++
++* When using a cloudslot number **above** 125, the following configuration is needed to communicate to your JMS.
      ** 3.74.209.20:443
      ** 3.76.127.155:443
      ** 3.74.209.20:8443
      ** 3.76.127.155:8443
      ** 3.74.209.20:8444
--    ** 3.76.127.155:8444
--    ** 18.199.123.240:443
--    ** 18.184.211.189:443
--    ** 3.123.136.31:443
--    ** 3.66.44.69:443
--    ** 52.57.64.170:443
--    ** 63.182.102.95:443{{/warning}}
++    ** 3.76.127.155:8444{{/warning}}
  ===3.2 Installation Windows===
--When Windows is selected as the operating system, you need Windows Server 2022. Older Windows servers are **not** supported.
++Whenever Windows is selected as operating system, you need to have a Windows Server 2022 version. Older Windows servers are **not** supported.
++
  ==== 3.2.1 Docker Installation ====
--To install Docker on your machine, execute the following commands in PowerShell with administrative rights:
++To install or update docker on your machine, execute the following commands in powershell with administrative rights:
  {{code language="cmd"}}
--Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Install-update-docker/install-update-docker.ps1" -o install-update-docker-ce.ps1
--.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
++Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/Windows-Containers/Main/helpful_tools/Install-DockerCE/install-docker-ce.ps1" -o install-docker-ce.ps1
++.\install-docker-ce.ps1
  {{/code}}
--==== 3.2.2 Customization ====
++==== 3.2.2 Check installation ====
--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"]].
--
--{{warning}}Be aware that the customization will only take effect once you have restarted the machine.{{/warning}}
--
--===== 3.2.2.1 IP address range =====
--
--Below is the code needed to configure a different IP address range.
--
--{{code language="cmd"}}
--cd C:\ProgramData\Docker\config\daemon.json
--#Add the following lines
--{"fixed-cidr": "<ip-address>"}
--{{/code}}
--
--===== 3.2.2.2 Data location =====
--
--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:
--
--{{code language="cmd"}}
--cd C:\ProgramData\Docker\config\daemon.json
--#Add the following lines
--{
-- "data-root": "d:\\docker"
--}
--{{/code}}
--
--{{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}}
--
--==== 3.2.3 Check installation ====
--
  After executing the commands above, the server will restart if required. After the restart, execute the following command
  {{code language="cmd"}}
@@ -107,13 +107,13 @@
  docker ps
  {{/code}}
--If the command returns "command not found," please run the following command again.
++If the command returns that the command cannot be found, please run the following command again.
  {{code language="cmd"}}
--.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
++.\install-docker-ce.ps1
  {{/code}}
--==== 3.2.3 Verify Docker functionality ====
++==== 3.2.3 Verify docker functionality ====
  Execute the following command
@@ -127,59 +127,53 @@
  ==== 3.2.4 Install eMagiz Deploy Agent ====
--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"]]
++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"]]
--=== 3.3 Update Docker ===
--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:
++===3.3 Uninstall Docker===
++To uninstall docker from your machine, execute the following commands in powershell with administrative rights:
  {{code language="cmd"}}
--docker version
++Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Uninstall-docker/uninstall-docker.ps1" -o uninstall-docker-ce.ps1
  {{/code}}
--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:
++Example usage:
  {{code language="cmd"}}
--.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
++.\uninstall-docker-ce.ps1
  {{/code}}
--{{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}}
++{{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[[Cloud templates>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]].
++{{/info}}
--===3.4 Uninstall Docker===
--To uninstall Docker from your machine, execute the following commands in PowerShell with administrative rights:
++{{info}}
++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}}.
++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"]].
--{{code language="cmd"}}
--Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Uninstall-docker/uninstall-docker.ps1" -o uninstall-docker-ce.ps1
--{{/code}}
++{{warning}}
++Ignore the Uninstall section as it is outdated (For Windows Server 2016), instead refer to the previous section to Uninstall docker
++{{/warning}}
--Example usage:
++**Example usage of the Docker daemon file**: You maybe want the Docker daemon to keep images and containers in an alternate path (D:
++drive for example). To do so you can add the following attribute to the Docker daemon file:
  {{code language="cmd"}}
--.\uninstall-docker-ce.ps1
++{
++ "data-root": "d:\\docker"
++}
  {{/code}}
++If not specified, the default is {{code language="cmd"}}c:\programdata\docker{{/code}}
++
++{{/info}}
++
  == 4. Key takeaways ==
--* 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
++* 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
  * eMagiz has a specific agent that manages the download of that image to the on-premises server
--* 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.
++* 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.
  == 5. Suggested Additional Readings ==
--* [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]]
--** [[eMagiz Runtime Generation 3 (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]
--* [[Release Information (Menu)>>doc:Main.Release Information.WebHome||target="blank"]]
--** [[Environment Templates (Navigation)>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]]
--* [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
--** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]]
--*** [[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"]]
--*** [[eMagiz Deploy agent (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]]
--* [[Advanced (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]]
--** [[Lifecycle Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Lifecycle Management.WebHome||target="blank"]]
--*** [[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"]]
--* [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]]
--** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]]
--*** [[Install Docker for Linux (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-linux-installguide.WebHome||target="blank"]]
--* [[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"]]
  * Docker command line cheatsheet: [[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]]
  )))((({{toc/}}))){{/container}}{{/container}}