Changes for page Install Docker for Linux
Last modified by Erik Bakker on 2026/01/30 10:56
From version 23.1
edited by eMagiz
on 2022/11/11 09:38
on 2022/11/11 09:38
Change comment:
There is no comment for this version
To version 137.1
edited by Erik Bakker
on 2026/01/23 13:15
on 2026/01/23 13:15
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 Linux - 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 focusonhowtheinstallation requirements for on-premises deployments of eMagizruntimesthat arepart of thenewruntimearchitecture.Thenewruntimearchitectureusesacontainerizedapproachto deployruntimes.2 +In eMagiz's current runtime architecture, Docker technology plays a central role in deploying runtimes. eMagiz creates specific runtime images tailored for dockerized environments, streamlining deployment. This section focuses on preparing a Linux server for the installation of the eMagiz Deploy Agent, which facilitates downloading these runtime 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,111 +9,194 @@ 9 9 * Good understanding of eMagiz runtimes in general 10 10 11 11 == 2. Key concepts == 12 -In the newruntime 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.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 13 14 -In the below section the specificoperating systemsand versionsarediscussed ina sensethattheprerequisiteinstallationsaredescribed.Oncethe right installationisdone,refer tosection3.5 fortheinstallation of the eMagiz agentthatmanages theinteractionwith theeMagiz platform. That agentwill downloadthe created dockerimages that will bedeployedinthe Dockerenvironment.14 +In the below section the Linux 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 16 16 == 3. On-premises deployments == 17 - 18 -===3.1 Installation requirements Linux=== 19 19 20 -These are the requirements to allow the installation of the eMagiz Docker agent: 21 -* Ensure access to the following URLs is enabled 22 - ** registry.emagiz.com 23 - ** testing.emagiz.com 24 - ** Preferably the entry should be *.emagiz.com 25 -* Install latest version of Docker 26 -* Go to the next section around installing the eMagiz agent 18 +===3.1 General requirements=== 19 +These are the general requirements to allow the installation of the eMagiz Docker agent: 27 27 28 -===3.2 Installation requirements Windows Server 2022=== 21 +{{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"]]. 22 +{{/info}} 29 29 30 -These are the requirements to allow the installation of the eMagiz Docker agent: 31 -* Ensure access to the following URLs is enabled 32 - ** registry.emagiz.com 33 - ** testing.emagiz.com 24 +{{info}} 25 +* Standard configuration to ensure that communication between your server and eMagiz to ensure communication. 26 + ** registry.emagiz.com:443 27 + ** controlplane.emagiz.com:443 28 + ** controlplane-agent.emagiz.com:443 29 + ** controltower.emagiz.com:443 30 + ** controltower.kpn-dsh.com:443 31 + ** controlbus.emagiz.com:443 34 34 ** Preferably the entry should be *.emagiz.com 35 -* Install latest version of Docker 36 -* Validate if WSL 2.0 is properly installed 37 -* Go to the next section around installing the eMagiz agent 38 - 39 -===3.3 Installation requirements Windows Server 2019 version 1806=== 33 + ** Preferably the entry should be *.kpn-dsh.com{{/info}} 40 40 41 -These are the requirements to allow the installation of the eMagiz Docker agent: 42 -* Ensure access to the following URLs is enabled 43 - ** registry.emagiz.com 44 - ** testing.emagiz.com 45 - ** Preferably the entry should be *.emagiz.com 46 -* Enable Hyper-V in Windows Server 47 - ** 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. 48 - ** Restart windows 49 -* Install Docker Desktop on the Windows Server 50 - ** Please refer to this link: https://www.docker.com/products/docker-desktop/ 51 - ** Restart windows 52 -* Update Docker desktop configuration 53 - ** Go to settings, and enable ‘Expose daemon on tcp://localhost:2375’ without TLS 54 - ** Restart Docker 55 -* Open Powershell as Administrator 56 - ** Execute "C:\Program Files\Docker\Docker\DockerCli.exe" -SwitchLinuxEngine 57 - ** Execute Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux 58 - ** Execute curl.exe -L -o ubuntu-2004.appx https://aka.ms/wslubuntu2004 59 - ** Execute Add-AppxPackage .\ubuntu-2004.appx 60 - *** 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. 61 -* Ubuntu should now be a runnable program (press windows key, type ubuntu) 62 -* Open the ubuntu terminal, and finish the installation. 63 - ** After installation, execute: export DOCKER_HOST=tcp://localhost:2375 64 -* Go to the next section around installing the eMagiz agent 65 - 66 -===3.4 Installation requirements Windows Server 2012 R2 === 67 - 68 -These are the requirements to allow the installation of the eMagiz Docker agent: 69 -* Ensure access to the following URLs is enabled 70 - ** registry.emagiz.com 71 - ** testing.emagiz.com 72 - ** Preferably the entry should be *.emagiz.com 73 -* Install & enable Hyper-V in Windows Server 74 - ** 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. 75 - ** Restart windows 76 -* Download a ubuntu server 18.04 (https://releases.ubuntu.com/18.04/ubuntu-18.04.6-live-server-amd64.iso ) 77 -* Create a VM in HyperV. 78 - ** 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). 79 - ** Configure a virtual switch. 80 - ** Add a virtual Hard Disk with proper sizing (e.g. 30 GB) 81 - ** Install an operating system from bootable CD/DVD, ISO file 82 -* Install ubuntu downloaded previously on the VM 83 -* Install docker as per official ubuntu documentation (See https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository) on the VM 84 -* Go to the next section around installing the eMagiz agent 85 - 86 -=== 3.5 eMagiz agent installation agent === 87 - 88 -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. 35 +{{warning}} 36 +* When using **IP Whitelisting**, the following configuration is needed to communicate to your JMS. 37 + ** 35.158.46.28:443 38 + ** 3.74.190.88:443 39 + ** 35.158.46.28:8443 40 + ** 3.74.190.88:8443 41 + ** 35.158.46.28:8444 42 + ** 3.74.190.88:8444 43 + ** 3.74.209.20:443 44 + ** 3.76.127.155:443 45 + ** 3.74.209.20:8443 46 + ** 3.76.127.155:8443 47 + ** 3.74.209.20:8444 48 + ** 3.76.127.155:8444 49 + ** 18.199.123.240 50 + ** 18.184.211.189 51 + ** 3.123.136.31{{/warning}} 89 89 90 -After installing the agent, validate it runs by checking if a docker container runs on ubuntu. 91 -* wget https://download.docker.com/linux/static/stable/x86_64/docker-20.10.5.tgz 92 -* tar zxvf docker-20.10.5.tgz 93 -* cd docker 94 -* ./docker psg 53 +===3.2 Installation Linux=== 95 95 55 +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. 96 96 97 -== 4. Assignment == 57 +==== 3.2.1 Uninstall old versions ==== 58 +{{info}}Before you can install Docker Engine, you need to uninstall any conflicting packages. 98 98 99 -Check out the cheatcheet for Docker command line: 100 - 101 -[[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]] 60 +Your Linux distribution may provide unofficial Docker packages, which may conflict with the official packages provided by Docker. You must uninstall these packages before you install the official version of Docker Engine.{{/info}} 102 102 103 -== 5. Key takeaways == 62 +{{code language="cmd"}} 63 +sudo apt remove $(dpkg --get-selections docker.io docker-compose docker-compose-v2 docker-doc podman-docker containerd runc | cut -f1) 64 +{{/code}} 104 104 105 -* 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 106 -* eMagiz has a specific agent that manages the download of that image to the on-premises server 107 -* 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. 66 +==== 3.2.1 Set up Docker's apt repository ==== 108 108 68 +{{code language="cmd"}} 69 +# Add Docker's official GPG key: 70 +sudo apt-get update 71 +sudo apt-get install ca-certificates curl 72 +sudo install -m 0755 -d /etc/apt/keyrings 73 +sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc 74 +sudo chmod a+r /etc/apt/keyrings/docker.asc 109 109 76 +# Add the repository to Apt sources: 77 +echo \ 78 + "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \ 79 + $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \ 80 + sudo tee /etc/apt/sources.list.d/docker.list > /dev/null 81 +sudo apt-get update 82 +{{/code}} 110 110 111 -== 6.Suggested AdditionalReadings==84 +==== 3.2.2 Install Docker ==== 112 112 113 -N/A 86 +To install a specific version of Docker Engine, start by listing the available versions in the repository: 87 + 88 +{{code language="cmd"}} 89 +apt list --all-versions docker-ce 90 + 91 +docker-ce/noble 5:29.1.5-1~ubuntu.24.04~noble <arch> 92 +docker-ce/noble 5:29.1.4-1~ubuntu.24.04~noble <arch> 93 +... 94 +{{/code}} 95 + 96 +Select the desired version and install: 97 +{{code language="cmd"}} 98 +VERSION_STRING=5:29.1.5-1~ubuntu.24.04~noble 99 +sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin 100 +{{/code}} 101 + 102 +==== 3.2.3 Customization ==== 103 + 104 +After installing Docker you have the option to stick with the standard configuration of Docker or you can opt to alter some specific settings. One setting that can be of particular interest is the setting that defines the IP address range your Docker installation will use to run the containers. 105 + 106 +===== 3.2.3.1 IP address range ===== 114 114 115 -== 7. Silent demonstration video == 108 +Below you can find the recommended values depending on the range which can be filled in the value <ip-address> below: 109 +* 10.0.0.1/8 110 +** advised value 10.25.0.1/16 111 +* 172.16.0.1/12 112 +** advised value 172.16.0.1/16 113 +* 192.168.0.1/16 114 +** advised value 192.168.0.1/16 116 116 117 -N/A 116 +{{code language="cmd"}} 117 +sudo nano /etc/docker/daemon.json 118 +#Add following lines 119 +{"bip": "<ip-address>"} 120 +{{/code}} 118 118 122 +{{warning}}Be aware that the customization will only take effect once you have restarted Docker.{{/warning}} 123 + 124 +==== 3.2.4 Verify succesfull installation of the Docker Engine ==== 125 + 126 +{{code language="cmd"}} 127 +sudo docker run hello-world 128 +{{/code}} 129 + 130 +{{info}} 131 + Requires ~335 Mb space to install 132 +{{/info}} 133 + 134 +==== 3.2.5 Install eMagiz Deploy Agent ==== 135 + 136 +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"]] 137 + 138 +=== 3.3 Update Docker === 139 +When you are advised to update your Docker version, you can follow the following procedure to update to a specific version of Docker Engine, start by listing the available versions in the repository: 140 + 141 +{{code language="cmd"}} 142 +apt list --all-versions docker-ce 143 + 144 +docker-ce/noble 5:29.1.5-1~ubuntu.24.04~noble <arch> 145 +docker-ce/noble 5:29.1.4-1~ubuntu.24.04~noble <arch> 146 +...{{/code}} 147 + 148 +Select the desired version and install. 149 + 150 +{{code language="cmd"}} 151 +VERSION_STRING=5:29.1.5-1~ubuntu.24.04~noble 152 +sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin 153 +{{/code}} 154 + 155 +===3.4 Uninstall Docker=== 156 +To uninstall Docker from your machine, execute the following command. 157 + 158 +{{code language="cmd"}} 159 +sudo apt purge docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin docker-ce-rootless-extras 160 +{{/code}} 161 + 162 +{{warning}}Images, containers, volumes, or custom configuration files on your host aren't automatically removed. To delete all images, containers, and volumes: 163 + 164 +{{code language="cmd"}} 165 +sudo rm -rf /var/lib/docker 166 +sudo rm -rf /var/lib/containerd 167 +Remove source list and keyrings 168 +{{/code}} 169 + 170 +{{code language="cmd"}} 171 + sudo rm /etc/apt/sources.list.d/docker.sources 172 + sudo rm /etc/apt/keyrings/docker.asc 173 +{{/code}} 174 +{{/warning}} 175 +== 4. Key takeaways == 176 + 177 +* 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 178 +* eMagiz has a specific agent that manages the download of that image to the on-premises server 179 +* 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. 180 + 181 +== 5. Suggested Additional Readings == 182 + 183 +* [[Docker official installation guide (External)>>https://docs.docker.com/engine/install/ubuntu/||target="blank"]] 184 +** [[Fundamentals (Navigation)>>doc:Main.eMagiz Academy.Fundamentals.WebHome||target="blank"]] 185 +*** [[eMagiz Runtime Generation 3 (Explanation)>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] 186 +* [[Release Information (Menu)>>doc:Main.Release Information.WebHome||target="blank"]] 187 +** [[Environment Templates (Navigation)>>doc:Main.Release Information.Cloud Templates.WebHome||target="blank"]] 188 +* [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] 189 +** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]] 190 +*** [[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"]] 191 +*** [[eMagiz Deploy agent (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-deploy-agent.WebHome||target="blank"]] 192 +* [[Advanced (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.WebHome||target="blank"]] 193 +** [[Lifecycle Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Lifecycle Management.WebHome||target="blank"]] 194 +*** [[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"]] 195 +* [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] 196 +** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]] 197 +*** [[Install Docker for Windows (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-onpremises-server-windows-installguide.WebHome||target="blank"]] 198 +* [[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"]] 199 +* Docker command line cheatsheet: [[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]] 200 + 201 + 119 119 )))((({{toc/}}))){{/container}}{{/container}}