Changes for page Install Docker for Linux
Last modified by Erik Bakker on 2025/04/18 13:54
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -On-premise sdeploymentnew runtimearchitecture1 +On-premise Install Guide - Content
-
... ... @@ -9,45 +9,134 @@ 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 envir ionments.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 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. 5for the installation of the eMagizportainer 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.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 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: 18 +===3.1 General requirements=== 19 + 20 +These are the general requirements to allow the installation of the eMagiz Docker agent: 21 21 * Ensure access to the following URLs is enabled 22 - ** registry.emagiz.com 23 - ** t esting.emagiz.com22 + ** registry.emagiz.com:8443 23 + ** controlplane.emagiz.com:8000 24 24 ** Preferably the entry should be *.emagiz.com 25 -* Install latest version of Docker 26 26 27 -===3.2 Installation requirements Windows Server 2022=== 26 + 27 +===3.2 Installation requirements Linux=== 28 28 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 32 + 33 +===3.3 Installation requirements Windows Server 2022=== 34 + 29 29 These are the requirements to allow the installation of the eMagiz Docker agent: 30 -* Ensure access to the following URLs is enabled 31 - ** registry.emagiz.com 32 - ** testing.emagiz.com 33 - ** Preferably the entry should be *.emagiz.com 34 -* Install latest version of Docker 36 +* Install latest version of Docker Desktop from {{code}}https://www.docker.com/products/docker-desktop/{{/code}} 35 35 * Validate if WSL 2.0 is properly installed 38 +* Go to the next section around installing the eMagiz Docker agent 39 + 40 +===3.3 Installation requirements Windows Server 2022 (without Docker Desktop) === 36 36 37 - ===3.3InstallationrequirementsWindowsServer 2019 version1806===42 +**Step 1: Install linux distribution** 38 38 44 +{{code language="cmd"}} 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 49 +{{/code}} 50 + 51 + 52 +**Step 2: Install Docker ** 53 + 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}} 60 + 61 +{{info}} 62 + Requires ~335 Mb space to install 63 +{{/info}} 64 + 65 +**Step 3: Install Java ** 66 + 67 +{{code language="cmd"}} 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 72 +{{/code}} 73 + 74 +{{info}} 75 + Requires ~335 Mb space to install 76 +{{/info}} 77 + 78 +**Step 4: Ensure Docker is autostarted with WSL ** 79 + 80 +{{code language="cmd"}} 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" 88 +{{/code}} 89 + 90 +**Step 5: Add user to Docker group ** 91 + 92 +{{code language="cmd"}} 93 +sudo visudo 94 + 95 + #Add following lines 96 + 97 + # Don't ask for password 98 + %docker ALL=(ALL) NOPASSWD: /usr/bin/dockerd 99 +{{/code}} 100 + 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 103 + 104 +First, locate the config file or add it to the location %USERPROFILE%. The name should be .wslconfig (no extension) 105 +{{code language="cmd"}} 106 + #Add following lines 107 + 108 + # Settings apply across all Linux distros running on WSL 2 109 + [wsl2] 110 + # Limits VM memory to use no more than 4 GB, this can be set as whole numbers using GB or MB 111 + memory=16GB 112 + # Sets the VM to use two virtual processors 113 + processors=2 114 +{{/code}} 115 + 116 + 117 + 118 +(Exit WSL: wsl --shutdown) 119 + 120 + 121 +===3.4 Installation requirements Windows Server 2019 version >1806=== 122 + 39 39 These are the requirements to allow the installation of the eMagiz Docker agent: 40 -* Ensure access to the following URLs is enabled 41 - ** registry.emagiz.com 42 - ** testing.emagiz.com 43 - ** Preferably the entry should be *.emagiz.com 124 +* Install latest version of Docker Desktop from https://www.docker.com/products/docker-desktop/ 125 +* Validate if WSL 2.0 is properly installed 126 +* Go to the next section around installing the eMagiz Docker agent 127 + 128 +===3.5 Installation requirements Windows Server 2019 version 1806=== 129 + 130 +These are the requirements to allow the installation of the eMagiz Docker agent: 44 44 * Enable Hyper-V in Windows Server 45 45 ** 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. 46 46 ** Restart windows 134 +* Cross check is WSL 2.0 is installed 135 + ** Use this command to get WSL 2.0: Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux 47 47 * Install Docker Desktop on the Windows Server 48 48 ** Please refer to this link: https://www.docker.com/products/docker-desktop/ 49 49 ** Restart windows 50 -* Update Docker desktop configuration139 +* Update Docker Desktop configuration 51 51 ** Go to settings, and enable ‘Expose daemon on tcp://localhost:2375’ without TLS 52 52 ** Restart Docker 53 53 * Open Powershell as Administrator ... ... @@ -59,14 +59,11 @@ 59 59 * Ubuntu should now be a runnable program (press windows key, type ubuntu) 60 60 * Open the ubuntu terminal, and finish the installation. 61 61 ** After installation, execute: export DOCKER_HOST=tcp://localhost:2375 62 - 63 -===3.4 Installation requirements Windows Server 2012 R2 === 64 - 151 +* Go to the next section around installing the eMagiz Docker agent 152 + 153 +===3.6 Installation requirements Windows Server 2012 R2 === 154 + 65 65 These are the requirements to allow the installation of the eMagiz Docker agent: 66 -* Ensure access to the following URLs is enabled 67 - ** registry.emagiz.com 68 - ** testing.emagiz.com 69 - ** Preferably the entry should be *.emagiz.com 70 70 * Install & enable Hyper-V in Windows Server 71 71 ** 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. 72 72 ** Restart windows ... ... @@ -78,15 +78,20 @@ 78 78 ** Install an operating system from bootable CD/DVD, ISO file 79 79 * Install ubuntu downloaded previously on the VM 80 80 * Install docker as per official ubuntu documentation (See https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository) on the VM 81 - 82 -=== 3.5 Installation agent === 83 - 84 -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. 167 +* Go to the next section around installing the eMagiz agent 85 85 169 +=== 3.7 eMagiz Docker agent installation === 170 + 171 +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. 172 + 173 +[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-installguide-deployagent.png]] 174 + 175 +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. 176 + 86 86 == 4. Assignment == 87 87 88 88 Check out the cheatcheet for Docker command line: 89 - 180 + 90 90 [[image:Main.Images.Microlearning.WebHome@docker-cheatsheet.png]] 91 91 92 92 == 5. Key takeaways == ... ... @@ -93,7 +93,7 @@ 93 93 94 94 * 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 95 95 * eMagiz has a specific agent that manages the download of that image to the on-premises server 96 -* 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. 187 +* 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. 97 97 98 98 99 99