Changes for page Install Docker for Windows
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
on 2024/12/17 12:20
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 -Install Docker for Windows1 +On-premise Install Guide - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. BasElzinga1 +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, whichsresponsiblefordownloading 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,160 +9,190 @@ 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 Windowsvariantcribed intermsofhowtopreparehe 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 -{{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:443 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 24 24 ** controlplane.emagiz.com:8000 25 - ** controlplane-agent.emagiz.com:8000 26 - ** controltower.emagiz.com:443 27 - ** controltower.kpn-dsh.com:443 28 - ** controlbus.emagiz.com:443 29 29 ** Preferably the entry should be *.emagiz.com 30 - ** Preferably the entry should be *.kpn-dsh.com{{/info}} 31 31 32 -{{warning}} 33 -* When using cloudslot number **equal to or below** 125, the following configuration is needed to communicate to your JMS. 34 - ** 35.158.46.28:443 35 - ** 3.74.190.88:443 36 - ** 35.158.46.28:8443 37 - ** 3.74.190.88:8443 38 - ** 35.158.46.28:8444 39 - ** 3.74.190.88:8444 40 - ** 18.199.123.240 41 - ** 18.184.211.189 42 - ** 3.123.136.31 26 + 27 +===3.2 Installation requirements Linux=== 43 43 44 -* When using a cloudslot number **above** 125, the following configuration is needed to communicate to your JMS. 45 - ** 3.74.209.20:443 46 - ** 3.76.127.155:443 47 - ** 3.74.209.20:8443 48 - ** 3.76.127.155:8443 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}} 29 +* Whenever Linux is selected as operating system, the latest version of Ubuntu will work 30 +* Install latest version of the Docker engine - see for instance {{code}}https://docs.docker.com/engine/install/ubuntu/{{/code}} 31 +* Go to the next section around installing the eMagiz agent 54 54 55 -===3.2 Installation Windows=== 56 -Whenever Windows is selected as operating system, you need to have a Windows Server 2022 version. Older Windows servers are **not** supported. 33 +===3.3 Installation requirements Windows Server 2022=== 57 57 35 +These are the requirements to allow the installation of the eMagiz Docker agent: 36 +* Install latest version of Docker Desktop from {{code}}https://www.docker.com/products/docker-desktop/{{/code}} 37 +* Validate if WSL 2.0 is properly installed 38 +* Go to the next section around installing the eMagiz Docker agent 58 58 59 -==== 3.2.1 Docker Installation ==== 60 -To install or update docker on your machine, execute the following commands in powershell with administrative rights: 40 +===3.3 Installation requirements Windows Server 2022 (without Docker Desktop) === 41 + 42 +**Step 1: Install linux distribution** 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 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 65 65 {{/code}} 66 66 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 -{{/info}} 69 69 70 - ====3.2.2Customization====52 +**Step 2: Install Docker ** 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"]]. 54 +{{code language="cmd"}} 55 + curl -fsSL https://download.docker.com/linux/${ID}/gpg | sudo tee /etc/apt/trusted.gpg.d/docker.asc 56 + echo "deb [arch=amd64] https://download.docker.com/linux/${ID} ${VERSION_CODENAME} stable" | sudo tee /etc/apt/sources.list.d/docker.list 57 + sudo apt update 58 + sudo apt install docker-ce docker-ce-cli containerd.io 59 +{{/code}} 73 73 74 -{{warning}}Be aware that the customization will only take effect once you have restarted the machine.{{/warning}} 61 +{{info}} 62 + Requires ~335 Mb space to install 63 +{{/info}} 75 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. 65 +**Step 3: Install Java ** 79 79 80 80 {{code language="cmd"}} 81 -cd C:\ProgramData\Docker\config\daemon.json 82 -#Add following lines 83 -{"fixed-cidr": "<ip-address>"} 68 + wget -O - https://packages.adoptium.net/artifactory/api/gpg/key/public | sudo apt-key add - 69 + 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 70 + sudo apt update # update if you haven't already 71 + sudo apt install temurin-8-jdk 84 84 {{/code}} 85 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 onyour 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:74 +{{info}} 75 + Requires ~335 Mb space to install 76 +{{/info}} 89 89 78 +**Step 4: Ensure Docker is autostarted with WSL ** 79 + 90 90 {{code language="cmd"}} 91 -cd C:\ProgramData\Docker\config\daemon.json 92 -#Add following lines 93 -{ 94 - "data-root": "d:\\docker" 95 -} 81 +nano .bashrc 82 + 83 + #Add following lines to bashrc 84 + DOCKER_DISTRO="Ubuntu" 85 + DOCKER_LOG_DIR=$HOME/docker_logs 86 + mkdir -pm o=,ug=rwx "$DOCKER_LOG_DIR" 87 + /mnt/c/Windows/System32/wsl.exe -d $DOCKER_DISTRO sh -c "nohup sudo -b dockerd < /dev/null > $DOCKER_LOG_DIR/dockerd.log 2>&1" 96 96 {{/code}} 97 97 98 - {{warning}}Notethatwhenyouwant to createmultiple customizationstoyourconfiguration the resultin the daemon.json file should be a**valid** JSON structure{{/warning}}90 +**Step 5: Add user to Docker group ** 99 99 100 -==== 3.2.3 Check installation ==== 92 +{{code language="cmd"}} 93 +sudo visudo 101 101 102 - Afterexecutingthe commands above, the server will restart if required.After the restart, execute the followingcommand95 + #Add following lines 103 103 104 - {{codelanguage="cmd"}}105 -docker ps97 + # Don't ask for password 98 + %docker ALL=(ALL) NOPASSWD: /usr/bin/dockerd 106 106 {{/code}} 107 107 108 -If the command returns that the command cannot be found, please run the following command again. 101 +**Step 6: Update wsl config file ** 102 +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 109 109 104 +First, locate the config file or add it to the location %USERPROFILE%. The name should be .wslconfig (no extension) 105 + 110 110 {{code language="cmd"}} 111 -.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION 112 -{{/code}} 107 + #Add following lines 108 + 109 + # Settings apply across all Linux distros running on WSL 2 110 + [wsl2] 111 + # Limits VM memory to use no more than 4 GB, this can be set as whole numbers using GB or MB 112 + memory=16GB 113 + # Sets the VM to use two virtual processors 114 + processors=2 115 +{{/code}} 113 113 114 -==== 3.2.3 Verify docker functionality ==== 117 +**Step 7: Auto start the linux subsystem when server restarts ** 118 + 115 115 116 - Executethe followingcommand120 +===3.4 Installation requirements Windows Server 2019 version >1806=== 117 117 118 -{{code language="cmd"}} 119 -docker ps 120 -{{/code}} 122 +These are the requirements to allow the installation of the eMagiz Docker agent: 123 +* Install latest version of Docker Desktop from https://www.docker.com/products/docker-desktop/ 124 +* Validate if WSL 2.0 is properly installed 125 +* Go to the next section around installing the eMagiz Docker agent 121 121 122 - Theresultfthiscall shouldshowthefollowing:127 +===3.5 Installation requirements Windows Server 2019 version 1806=== 123 123 124 -[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-server-windows-installguide--correct-result.png]] 129 +These are the requirements to allow the installation of the eMagiz Docker agent: 130 +* Enable Hyper-V in Windows Server 131 + ** 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. 132 + ** Restart windows 133 +* Cross check is WSL 2.0 is installed 134 + ** Use this command to get WSL 2.0: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux 135 +* Install Docker Desktop on the Windows Server 136 + ** Please refer to this link: https://www.docker.com/products/docker-desktop/ 137 + ** Restart windows 138 +* Update Docker Desktop configuration 139 + ** Go to settings, and enable ‘Expose daemon on tcp://localhost:2375’ without TLS 140 + ** Restart Docker 141 +* Open Powershell as Administrator 142 + ** Execute "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchLinuxEngine 143 + ** Execute Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux 144 + ** Execute curl.exe -L -o ubuntu-2004.appx https://aka.ms/wslubuntu2004 145 + ** Execute Add-AppxPackage .\ubuntu-2004.appx 146 + *** 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. 147 +* Ubuntu should now be a runnable program (press windows key, type ubuntu) 148 +* Open the ubuntu terminal, and finish the installation. 149 + ** After installation, execute: export DOCKER_HOST=tcp://localhost:2375 150 +* Go to the next section around installing the eMagiz Docker agent 125 125 126 -=== =3.2.4InstalleMagiz DeployAgent ====152 +===3.6 Installation requirements Windows Server 2012 R2 === 127 127 128 -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"]] 154 +These are the requirements to allow the installation of the eMagiz Docker agent: 155 +* Install & enable Hyper-V in Windows Server 156 + ** 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. 157 + ** Restart windows 158 +* Download a ubuntu server 18.04 (https://releases.ubuntu.com/18.04/ubuntu-18.04.6-live-server-amd64.iso ) 159 +* Create a VM in HyperV. 160 + ** 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). 161 + ** Configure a virtual switch. 162 + ** Add a virtual Hard Disk with proper sizing (e.g. 30 GB) 163 + ** Install an operating system from bootable CD/DVD, ISO file 164 +* Install ubuntu downloaded previously on the VM 165 +* Install docker as per official ubuntu documentation (See https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository) on the VM 166 +* Go to the next section around installing the eMagiz agent 129 129 130 -===3.3 Uninstall Docker=== 131 -To uninstall docker from your machine, execute the following commands in powershell with administrative rights: 168 +=== 3.7 eMagiz Docker agent installation === 132 132 133 -{{code language="cmd"}} 134 -Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Uninstall-docker/uninstall-docker.ps1" -o uninstall-docker-ce.ps1 135 -{{/code}} 170 +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 under Deploy Architecture. At the runtime connector, there is a right click option called Deploy Agent. That presents either the command or the location where that agent is installed. 136 136 137 - Example:172 +[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-installguide-deployagent.png]] 138 138 139 -{{code language="cmd"}} 140 -.\uninstall-docker-ce.ps1 141 -{{/code}} 174 +After installing the agent, you can use the Docker cheat sheet below to see if the docker containers are running and/or images are available. 142 142 143 -== 4. Keytakeaways==176 +== 4. Assignment == 144 144 178 +Check out the cheatcheet for Docker command line: 179 + 180 +[[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]] 181 + 182 +== 5. Key takeaways == 183 + 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 146 146 * eMagiz has a specific agent that manages the download of that image to the on-premises server 147 147 * 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. 148 148 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 -* Docker command line cheatsheet: [[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]] 167 167 190 +== 6. Suggested Additional Readings == 191 + 192 +N/A 193 + 194 +== 7. Silent demonstration video == 195 + 196 +N/A 197 + 168 168 )))((({{toc/}}))){{/container}}{{/container}}