Changes for page Install Docker for Windows
Last modified by Erik Bakker on 2026/01/30 10:56
From version 19.1
edited by eMagiz
on 2022/11/11 09:27
on 2022/11/11 09:27
Change comment:
There is no comment for this version
To version 136.1
edited by Erik Bakker
on 2024/11/29 08:30
on 2024/11/29 08:30
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - On-premises deployment newruntimearchitecture1 +Install Docker for Windows - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e Magiz1 +XWiki.ebakker - Content
-
... ... @@ -1,5 +1,5 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 -In thismicrolearning, wewill focusonhowtheinstallationrequirementsfor on-premisesdeploymentsof eMagiz runtimes that are partofthenewruntimearchitecture.Thenewruntimearchitectureusesa containerizedapproachtodeployruntimes.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. 3 3 4 4 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 5 5 ... ... @@ -9,102 +9,164 @@ 9 9 * Good understanding of eMagiz runtimes in general 10 10 11 11 == 2. Key concepts == 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 envirionments 13 - 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. 13 + 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 + 14 14 == 3. On-premises deployments == 15 - 16 -===3.1 Installation requirements Linux=== 17 17 18 -These are the requirements to allow the installation of the eMagiz Docker agent: 19 -* Ensure access to the following URLs is enabled 20 - ** registry.emagiz.com 21 - ** testing.emagiz.com 18 +===3.1 General requirements=== 19 + 20 +{{info}} 21 +* Standard configuration to ensure that communication between your server and eMagiz to ensure communication. 22 + ** registry.emagiz.com:443 23 + ** controlplane.emagiz.com:8000 24 + ** controltower.kpn-dsh.com:443 22 22 ** Preferably the entry should be *.emagiz.com 23 -* InstalllatestversionofDocker26 + ** Preferably the entry should be *.kpn-dsh.com{{/info}} 24 24 25 -===3.2 Installation requirements Windows Server 2022=== 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 26 26 27 -These are the requirements to allow the installation of the eMagiz Docker agent: 28 -* Ensure access to the following URLs is enabled 29 - ** registry.emagiz.com 30 - ** testing.emagiz.com 31 - ** Preferably the entry should be *.emagiz.com 32 -* Install latest version of Docker 33 -* Validate if WSL 2.0 is properly installed 35 +* When using cloudslot number **equal to or below** 125, the following configuration is needed to communicate to your JMS. 36 + ** 35.158.46.28:443 37 + ** 3.74.190.88:443 38 + ** 35.158.46.28:8443 39 + ** 3.74.190.88:8443 40 + ** 35.158.46.28:8444 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 + ** 3.74.209.20:443 48 + ** 3.76.127.155:443 49 + ** 3.74.209.20:8443 50 + ** 3.76.127.155:8443 51 + ** 3.74.209.20:8444 52 + ** 3.76.127.155:8444 53 + ** 18.199.123.240 54 + ** 18.184.211.189 55 + ** 3.123.136.31{{/warning}} 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 + 60 + 61 +==== 3.2.1 Docker Installation ==== 62 +To install or update docker on your machine, execute the following commands in powershell with administrative rights: 63 + 64 +{{code language="cmd"}} 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 +.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION 67 +{{/code}} 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 +==== 3.2.2 Customization ==== 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}} 77 + 78 +===== 3.2.2.1 IP address range ===== 34 34 35 -===3.3 Installation requirements Windows Server 2019 version 1806=== 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 36 36 37 -These are the requirements to allow the installation of the eMagiz Docker agent: 38 -* Ensure access to the following URLs is enabled 39 - ** registry.emagiz.com 40 - ** testing.emagiz.com 41 - ** Preferably the entry should be *.emagiz.com 42 -* Enable Hyper-V in Windows Server 43 - ** Go to Server Manager, Manage (top right), enable roles and features, select the desired roles and server selections. In the Features section, enable Hyper-V. 44 - ** Restart windows 45 -* Install Docker Desktop on the Windows Server 46 - ** Please refer to this link: https://www.docker.com/products/docker-desktop/ 47 - ** Restart windows 48 -* Update Docker desktop configuration 49 - ** Go to settings, and enable ‘Expose daemon on tcp://localhost:2375’ without TLS 50 - ** Restart Docker 51 -* Open Powershell as Administrator 52 - ** Execute "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchLinuxEngine 53 - ** Execute Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux 54 - ** Execute curl.exe -L -o ubuntu-2004.appx https://aka.ms/wslubuntu2004 55 - ** Execute Add-AppxPackage .\ubuntu-2004.appx 56 - *** If errors occur, please consult https://learn.microsoft.com/en-us/windows/wsl/install-on-server. Rename the file to a zip, expand it, and add it to the path variable. 57 -* Ubuntu should now be a runnable program (press windows key, type ubuntu) 58 -* Open the ubuntu terminal, and finish the installation. 59 - ** After installation, execute: export DOCKER_HOST=tcp://localhost:2375 88 +{{code language="cmd"}} 89 +sudo nano /etc/docker/daemon.json 90 +#Add following lines 91 +{"bip": "<ip-address>"} 92 +{{/code}} 60 60 61 -===3. 4Installationrequirements Windows Server 2012 R2===94 +===== 3.2.2.2 Data location ===== 62 62 63 -These are the requirements to allow the installation of the eMagiz Docker agent: 64 -* Ensure access to the following URLs is enabled 65 - ** registry.emagiz.com 66 - ** testing.emagiz.com 67 - ** Preferably the entry should be *.emagiz.com 68 -* Install & enable Hyper-V in Windows Server 69 - ** Go to Server Manager, Manage (top right), enable roles and features, select the desired roles and server selections. In the Features section, enable Hyper-V. 70 - ** Restart windows 71 -* Download a ubuntu server 18.04 (https://releases.ubuntu.com/18.04/ubuntu-18.04.6-live-server-amd64.iso ) 72 -* Create a VM in HyperV. 73 - ** For this, choose Generation 1, the amount of memory you want to assign to ubuntu and thus to the containers. Please consider the overhead for memory as well (such as OS). 74 - ** Configure a virtual switch. 75 - ** Add a virtual Hard Disk with proper sizing (e.g. 30 GB) 76 - ** Install an operating system from bootable CD/DVD, ISO file 77 -* Install ubuntu downloaded previously on the VM 78 -* Install docker as per official ubuntu documentation (See https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository) on the VM 79 - 80 -=== 3.5 Installation agent === 81 - 82 -eMagiz needs to install a specific agent in the Docker instance that allows to download runtime images that needs to be installed on the Docker instance. The specific command to run inside the Docker instance is specific for the machine that is configured inside eMagiz Design & Deploy Architectures. It can be found inside the eMagiz iPaaS portal or is available upon request. Once that agent is installed, the image that is generated for every eMagiz release can be downloaded and installed in the Docker instance. 83 - 84 -=== 3.3 Cloud architecture for API Gateway === 85 - 86 -[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-install-runtime-images.png]] 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: 87 87 88 -== 4. Assignment == 98 +{{code language="cmd"}} 99 +{ 100 + "data-root": "d:\\docker" 101 +} 102 +{{/code}} 89 89 90 -Check out the cheatcheet for Docker command line: 91 - 92 -[[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]] 104 +==== 3.2.3 Check installation ==== 93 93 94 - ==5. Keytakeaways==106 +After executing the commands above, the server will restart if required. After the restart, execute the following command 95 95 96 - * eMagiz uses runtime images todeployemagiz runtime on dockerized environments. The runtime imageholds all the information andcomponents requiredto run the runtime97 - * eMagiz has a specific agent that manages thedownload of that imageto the on-premises server98 - * The firewall of the on-premises environment should allow outgoing trafficwithout any restriction. In case that is notdesirable, eMagiz can provide the addresses and ports needed to setup the right firewall rules.108 +{{code language="cmd"}} 109 +docker ps 110 +{{/code}} 99 99 112 +If the command returns that the command cannot be found, please run the following command again. 100 100 114 +{{code language="cmd"}} 115 +.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION 116 +{{/code}} 101 101 102 -== 6.SuggestedAdditionalReadings==118 +==== 3.2.3 Verify docker functionality ==== 103 103 104 -N/A 105 - 106 -== 7. Silent demonstration video == 120 +Execute the following command 107 107 108 -N/A 122 +{{code language="cmd"}} 123 +docker ps 124 +{{/code}} 109 109 126 +The result of this call should show the following: 127 + 128 +[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-server-windows-installguide--correct-result.png]] 129 + 130 +==== 3.2.4 Install eMagiz Deploy Agent ==== 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"]] 133 + 134 +===3.3 Uninstall Docker=== 135 +To uninstall docker from your machine, execute the following commands in powershell with administrative rights: 136 + 137 +{{code language="cmd"}} 138 +Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Uninstall-docker/uninstall-docker.ps1" -o uninstall-docker-ce.ps1 139 +{{/code}} 140 + 141 +Example usage: 142 + 143 +{{code language="cmd"}} 144 +.\uninstall-docker-ce.ps1 145 +{{/code}} 146 + 147 +== 4. Key takeaways == 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 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. 152 + 153 +== 5. Suggested Additional Readings == 154 + 155 +* [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]] 156 +** [[eMagiz Runtime Generation 3 (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] 157 +* [[Release Information (Menu)>>doc:Main.Release Information.WebHome||target="blank"]] 158 +** [[Environment Templates (Navigation)>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] 159 +* [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] 160 +** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]] 161 +*** [[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"]] 162 +*** [[eMagiz Deploy agent (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]] 163 +* [[Advanced (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]] 164 +** [[Lifecycle Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Lifecycle Management.WebHome||target="blank"]] 165 +*** [[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"]] 166 +* [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] 167 +** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]] 168 +*** [[Install Docker for Linux (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-linux-installguide.WebHome||target="blank"]] 169 +* [[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"]] 170 +* Docker command line cheatsheet: [[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]] 171 + 110 110 )))((({{toc/}}))){{/container}}{{/container}}