Changes for page Install Docker for Windows
Last modified by Erik Bakker on 2026/01/23 13:45
From version 142.1
edited by Erik Bakker
on 2026/01/23 12:50
on 2026/01/23 12:50
Change comment:
There is no comment for this version
To version 65.1
edited by eMagiz
on 2023/02/07 12:38
on 2023/02/07 12:38
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 - InstallDockerforWindows1 +Pre-requisite installation for on-premises servers - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e bakker1 +XWiki.eMagiz - Content
-
... ... @@ -1,5 +1,5 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 -In eMagiz's currentruntimearchitecture,Dockertechnologyisutilizedto deployruntimesefficiently.eMagizprovides specific runtimeimages thatcan bedeployedwithin dockerizedenvironments.This section outlinesthestepsneeded to prepare a Windowsserver for the installation of theeMagiz Deploy Agent, whichisresponsiblefordownloading theseimagesfromtheeMagizinfrastructure.2 +In this microlearning, we will focus on how the installation requirements for on-premises deployments of eMagiz runtimes that are part of the new runtime architecture. The new runtime architecture uses a containerized approach to deploy runtimes. 3 3 4 4 Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 5 5 ... ... @@ -9,168 +9,189 @@ 9 9 * Good understanding of eMagiz runtimes in general 10 10 11 11 == 2. Key concepts == 12 -In the currentruntime 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 Windowsvariantis described intermsofhowtopreparethe servertoallowthe[[eMagizDeployAgent>>doc:Main.eMagizAcademy.Microlearnings.IntermediateLevel.eMagizRuntime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]]tobeinstalled. That agentallowstodownload imagesfromthe eMagizinfrastructure.15 - 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 + 14 +In the below section the specific operating systems and versions are discussed in a sense that the prerequisite installations are described. Once the right installation is done, refer to section 3.7 for the installation of the eMagiz agent that manages the interaction with the eMagiz platform. That agent will download the created docker images that will be deployed in the Docker environment. 15 + 16 16 == 3. On-premises deployments == 17 17 18 18 ===3.1 General requirements=== 19 + 20 +These are the general requirements to allow the installation of the eMagiz Docker agent: 21 +* Ensure access to the following URLs is enabled 22 + ** registry.emagiz.com:8443 23 + ** controlplane.emagiz.com:8000 24 + ** Preferably the entry should be *.emagiz.com 19 19 20 - {{info}}Itisadvised to use Docker version 24.0.7 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"]].21 - {{/info}}26 + 27 +===3.2 Installation requirements Linux=== 22 22 23 -{{info}} 24 -* Standard configuration to ensure that communication between your server and eMagiz to ensure communication. 25 - ** registry.emagiz.com:443 26 - ** controlplane.emagiz.com:443 27 - ** controlplane-agent.emagiz.com:443 28 - ** controltower.emagiz.com:443 29 - ** controltower.kpn-dsh.com:443 30 - ** controlbus.emagiz.com:443 31 - ** Preferably the entry should be *.emagiz.com 32 - ** Preferably the entry should be *.kpn-dsh.com{{/info}} 29 +Whenever Linux is selected as operating system, the latest version of Ubuntu will work. Other Linux distributions will also work such as Debian or Red Hat. 30 +**Step 1: Install linux distribution** 31 +Follow all steps in section 3.4 33 33 34 -{{warning}} 35 -* When using **IP Whitelisting**, 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 - ** 3.74.209.20:443 43 - ** 3.76.127.155:443 44 - ** 3.74.209.20:8443 45 - ** 3.76.127.155:8443 46 - ** 3.74.209.20:8444 47 - ** 3.76.127.155:8444 48 - ** 18.199.123.240 49 - ** 18.184.211.189 50 - ** 3.123.136.31{{/warning}} 33 +**Step 2: Install eMagiz Deploy Agent** 34 +Install the eMagiz Deploy agent as can be found here 51 51 36 +===3.3 Installation requirements Windows Server 2022 === 52 52 38 +{{info}}Please note that this section also applies to Windows Server 2019 version >1806{{/info}} 53 53 54 -===3.2 Installation Windows=== 55 -When Windows is selected as the operating system, you need Windows Server 2022. Older Windows servers are **not** supported. 40 +The steps below will install a linux subsystem under Windows. In that Linux system, Docker and Java will be installed. Please note that the Windows server needs to be able to run Virtualized (either via BIOS setting or via Nested Virtualization). 56 56 57 -==== 3.2.1 Docker Installation ==== 58 -To install Docker on your machine, execute the following commands in PowerShell with administrative rights: 42 +**Step 1: Install linux distribution** 59 59 60 60 {{code language="cmd"}} 61 -Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Install-update-docker/install-update-docker.ps1" -o install-update-docker-ce.ps1 62 -.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION 45 + wsl --install -d Ubuntu 46 + sudo apt-get update 47 + sudo apt install --no-install-recommends apt-transport-https ca-certificates curl gnupg2 48 + . /etc/os-release 63 63 {{/code}} 64 64 65 -==== 3.2.2 Customization ==== 66 - 67 -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"]]. 68 - 69 -{{warning}}Be aware that the customization will only take effect once you have restarted the machine.{{/warning}} 70 - 71 -===== 3.2.2.1 IP address range ===== 51 +**Step 2: Configure linux system** 52 +Please see section 3.4 for these these steps 72 72 73 -Below is the code needed to configure a different IP address range. 54 +**Step 3: Update wsl config file ** 55 +In this step we need to add or update the WSL config file that manages the resources of the Linux subsystem. Important resources to manage are the assigned memory and number of processors. For memory we recommend to review the mempory settings for the runtime that need to run on this server and add 762 MB to the total value of the heap and non-heap of these runtimes. For processor we recommend to set the value to 2 - depending on the amount of processors available on that machine 74 74 57 +First, locate the config file or add it to the location %USERPROFILE%. The name should be .wslconfig (no extension) 58 + 75 75 {{code language="cmd"}} 76 -cd C:\ProgramData\Docker\config\daemon.json 77 -#Add the following lines 78 -{"fixed-cidr": "<ip-address>"} 60 + #Add following lines 61 + 62 + # Settings apply across all Linux distros running on WSL 2 63 + [wsl2] 64 + # Limits VM memory to use no more than 4 GB, this can be set as whole numbers using GB or MB 65 + memory=16GB 66 + # Sets the VM to use two virtual processors 67 + processors=2 79 79 {{/code}} 80 80 81 -===== 3.2.2.2 Data location ===== 82 82 83 -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: 71 +**Step 4: Auto start the linux subsystem when Windows server restarts ** 72 + 73 +**Step 5: Install eMagiz Deploy Agent** 74 +Install the eMagiz Deploy agent as can be found here 75 + 76 + 77 +===3.4 Installation steps to configure Linux subsystem === 78 + 79 +**Step 1: Install Docker ** 84 84 85 85 {{code language="cmd"}} 86 -cd C:\ProgramData\Docker\config\daemon.json 87 -#Add the following lines 88 -{ 89 - "data-root": "d:\\docker" 90 -} 82 + curl -fsSL https://download.docker.com/linux/${ID}/gpg | sudo tee /etc/apt/trusted.gpg.d/docker.asc 83 + echo "deb [arch=amd64] https://download.docker.com/linux/${ID} ${VERSION_CODENAME} stable" | sudo tee /etc/apt/sources.list.d/docker.list 84 + sudo apt update 85 + sudo apt install docker-ce docker-ce-cli containerd.io 91 91 {{/code}} 92 92 93 -{{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}} 88 +{{info}} 89 + Requires ~335 Mb space to install 90 +{{/info}} 94 94 95 - ====3.2.3Check installation====92 +**Step 2: Install Java ** 96 96 97 -After executing the commands above, the server will restart if required. After the restart, execute the following command 98 - 99 99 {{code language="cmd"}} 100 -docker ps 95 + wget -O - https://packages.adoptium.net/artifactory/api/gpg/key/public | sudo apt-key add - 96 + echo "deb https://packages.adoptium.net/artifactory/deb $(awk -F= '/^VERSION_CODENAME/{print$2}' /etc/os-release) main" | sudo tee /etc/apt/sources.list.d/adoptium.list 97 + sudo apt update # update if you haven't already 98 + sudo apt install temurin-8-jdk 101 101 {{/code}} 102 102 103 -If the command returns "command not found," please run the following command again. 101 +{{info}} 102 + Requires ~335 Mb space to install 103 +{{/info}} 104 104 105 +**Step 3: Ensure Docker is autostarted with WSL ** 106 + 105 105 {{code language="cmd"}} 106 -.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION 108 +nano .bashrc 109 + 110 + #Add following lines to bashrc 111 + DOCKER_DISTRO="Ubuntu" 112 + DOCKER_LOG_DIR=$HOME/docker_logs 113 + mkdir -pm o=,ug=rwx "$DOCKER_LOG_DIR" 114 + /mnt/c/Windows/System32/wsl.exe -d $DOCKER_DISTRO sh -c "nohup sudo -b dockerd < /dev/null > $DOCKER_LOG_DIR/dockerd.log 2>&1" 107 107 {{/code}} 108 108 109 - ====3.2.3VerifyDockerfunctionality====117 +**Step 4: Add user to Docker group ** 110 110 111 -Execute the following command 112 - 113 113 {{code language="cmd"}} 114 -docker ps 115 -{{/code}} 120 +sudo visudo 116 116 117 - Theresultof this call shouldshow thefollowing:122 + #Add following lines 118 118 119 -[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-server-windows-installguide--correct-result.png]] 124 + # Don't ask for password 125 + %docker ALL=(ALL) NOPASSWD: /usr/bin/dockerd 126 +{{/code}} 120 120 121 - ====3.2.4InstalleMagizDeploy Agent ====128 + 122 122 123 -Install the eMagiz Deploy agentas describedinthis[[microlearning>>doc:Main.eMagizAcademy.Microlearnings.IntermediateLevel.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]]130 +===3.5 Installation requirements Windows Server 2019 version 1806=== 124 124 125 -==== 3.3 Update Docker ==== 126 -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: 132 +{{warning}}Please note that this section is under construction. Please contact us at productmanagement@emagiz.com{{/warning}} 127 127 128 -{{code language="cmd"}} 129 -docker version 130 -{{/code}} 134 +These are the requirements to allow the installation of the eMagiz Docker agent: 135 +* Enable Hyper-V in Windows Server 136 + ** 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. 137 + ** Restart windows 138 +* Cross check is WSL 2.0 is installed 139 + ** Use this command to get WSL 2.0: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux 140 +* Install Docker Desktop on the Windows Server 141 + ** Please refer to this link: https://www.docker.com/products/docker-desktop/ 142 + ** Restart windows 143 +* Update Docker Desktop configuration 144 + ** Go to settings, and enable ‘Expose daemon on tcp://localhost:2375’ without TLS 145 + ** Restart Docker 146 +* Open Powershell as Administrator 147 + ** Execute "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchLinuxEngine 148 + ** Execute Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux 149 + ** Execute curl.exe -L -o ubuntu-2004.appx https://aka.ms/wslubuntu2004 150 + ** Execute Add-AppxPackage .\ubuntu-2004.appx 151 + *** 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. 152 +* Ubuntu should now be a runnable program (press windows key, type ubuntu) 153 +* Open the ubuntu terminal, and finish the installation. 154 + ** After installation, execute: export DOCKER_HOST=tcp://localhost:2375 155 +* Go to the next section around installing the eMagiz Docker agent 131 131 132 - Whenthis returnsaversion **lower** thanthe advised versionshown below, youcan update Dockeron yourmachine. To doso,execute the following commandin PowerShell with administrativerights:157 +===3.6 Installation requirements Windows Server 2012 R2 === 133 133 134 -{{code language="cmd"}} 135 -.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION 136 -{{/code}} 159 +{{warning}}Please note that this section is under construction. Please contact us at productmanagement@emagiz.com{{/warning}} 137 137 138 -===3.4 Uninstall Docker=== 139 -To uninstall Docker from your machine, execute the following commands in PowerShell with administrative rights: 161 +These are the requirements to allow the installation of the eMagiz Docker agent: 162 +* Install & enable Hyper-V in Windows Server 163 + ** 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. 164 + ** Restart windows 165 +* Download a ubuntu server 18.04 (https://releases.ubuntu.com/18.04/ubuntu-18.04.6-live-server-amd64.iso ) 166 +* Create a VM in HyperV. 167 + ** 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). 168 + ** Configure a virtual switch. 169 + ** Add a virtual Hard Disk with proper sizing (e.g. 30 GB) 170 + ** Install an operating system from bootable CD/DVD, ISO file 171 +* Install ubuntu downloaded previously on the VM 172 +* Install docker as per official ubuntu documentation (See https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository) on the VM 173 +* Go to the next section around installing the eMagiz agent 140 140 141 -{{code language="cmd"}} 142 -Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Uninstall-docker/uninstall-docker.ps1" -o uninstall-docker-ce.ps1 143 -{{/code}} 175 +== 4. Assignment == 144 144 145 - Example usage:177 +Check out the cheatcheet for Docker command line: 146 146 147 -{{code language="cmd"}} 148 -.\uninstall-docker-ce.ps1 149 -{{/code}} 179 +[[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]] 150 150 151 -== 4. Key takeaways ==181 +== 5. Key takeaways == 152 152 153 -* eMagiz uses runtime images to deploy theeMagiz runtime onDockerized environments. The runtime image holds all the information and components required to run the runtime183 +* 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 154 154 * eMagiz has a specific agent that manages the download of that image to the on-premises server 155 -* The firewall of the on-premises environment should allow outgoing traffic without any restriction s. Ifthat is not desirable, eMagiz can provide the addresses and ports needed to setup theappropriatefirewall rules.185 +* 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. 156 156 157 -== 5. Suggested Additional Readings == 158 158 159 -* [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]] 160 -** [[eMagiz Runtime Generation 3 (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] 161 -* [[Release Information (Menu)>>doc:Main.Release Information.WebHome||target="blank"]] 162 -** [[Environment Templates (Navigation)>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] 163 -* [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] 164 -** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]] 165 -*** [[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"]] 166 -*** [[eMagiz Deploy agent (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]] 167 -* [[Advanced (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]] 168 -** [[Lifecycle Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Lifecycle Management.WebHome||target="blank"]] 169 -*** [[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"]] 170 -* [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] 171 -** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]] 172 -*** [[Install Docker for Linux (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-linux-installguide.WebHome||target="blank"]] 173 -* [[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"]] 174 -* Docker command line cheatsheet: [[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]] 175 175 189 +== 6. Suggested Additional Readings == 190 + 191 +N/A 192 + 193 +== 7. Silent demonstration video == 194 + 195 +N/A 196 + 176 176 )))((({{toc/}}))){{/container}}{{/container}}