Changes for page Install Docker for Linux

Last modified by Erik Bakker on 2025/04/18 13:54

From version 64.1
edited by eMagiz
on 2023/02/07 12:36
Change comment: There is no comment for this version
To version 60.1
edited by eMagiz
on 2023/02/07 12:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -26,17 +26,30 @@
26 26  
27 27  ===3.2 Installation requirements Linux===
28 28  
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
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 +* Install latest version of the Docker engine - see for instance this link below. For other Linux distributions similar install guides are available on this link.
32 32  
33 -**Step 2: Install eMagiz Deploy Agent**
34 -Install the eMagiz Deploy agent as can be found here
32 +{{code}}https://docs.docker.com/engine/install/ubuntu/{{/code}}
35 35  
36 -===3.3 Installation requirements Windows Server 2022 ===
37 37  
35 +* Install the eMagiz Deploy agent
36 +
37 +===3.3 Installation requirements Windows Server 2022 (Docker Desktop)===
38 +
38 38  {{info}}Please note that this section also applies to Windows Server 2019 version >1806{{/info}}
39 39  
41 +These are the requirements to allow the installation of the eMagiz Docker agent:
42 +* Install latest version of Docker Desktop from
43 +
44 +{{code}}https://www.docker.com/products/docker-desktop/{{/code}}
45 +
46 +* Validate if WSL 2.0 is properly installed
47 +* Install the eMagiz Deploy agent
48 +
49 +===3.3 Installation requirements Windows Server 2022 (without Docker Desktop) ===
50 +
51 +{{info}}Please note that this section also applies to Windows Server 2019 version >1806{{/info}}
52 +
40 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).
41 41  
42 42  **Step 1: Install linux distribution**
... ... @@ -48,37 +48,10 @@
48 48   . /etc/os-release
49 49  {{/code}}
50 50  
51 -**Step 2: Configure linux system**
52 -Please see section 3.4 for these these steps
53 -
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
56 56  
57 -First, locate the config file or add it to the location %USERPROFILE%. The name should be .wslconfig (no extension)
65 +**Step 2: Install Docker **
58 58  
59 59  {{code language="cmd"}}
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
68 -{{/code}}
69 -
70 -
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 **
80 -
81 -{{code language="cmd"}}
82 82   curl -fsSL https://download.docker.com/linux/${ID}/gpg | sudo tee /etc/apt/trusted.gpg.d/docker.asc
83 83   echo "deb [arch=amd64] https://download.docker.com/linux/${ID} ${VERSION_CODENAME} stable" | sudo tee /etc/apt/sources.list.d/docker.list
84 84   sudo apt update
... ... @@ -89,7 +89,7 @@
89 89   Requires ~335 Mb space to install
90 90  {{/info}}
91 91  
92 -**Step 2: Install Java **
78 +**Step 3: Install Java **
93 93  
94 94  {{code language="cmd"}}
95 95   wget -O - https://packages.adoptium.net/artifactory/api/gpg/key/public | sudo apt-key add -
... ... @@ -102,7 +102,7 @@
102 102   Requires ~335 Mb space to install
103 103  {{/info}}
104 104  
105 -**Step 3: Ensure Docker is autostarted with WSL **
91 +**Step 4: Ensure Docker is autostarted with WSL **
106 106  
107 107  {{code language="cmd"}}
108 108  nano .bashrc
... ... @@ -114,7 +114,7 @@
114 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"
115 115  {{/code}}
116 116  
117 -**Step 4: Add user to Docker group **
103 +**Step 5: Add user to Docker group **
118 118  
119 119  {{code language="cmd"}}
120 120  sudo visudo
... ... @@ -125,11 +125,30 @@
125 125   %docker ALL=(ALL) NOPASSWD: /usr/bin/dockerd
126 126  {{/code}}
127 127  
114 +**Step 6: Update wsl config file **
115 +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
116 +
117 +First, locate the config file or add it to the location %USERPROFILE%. The name should be .wslconfig (no extension)
118 +
119 +
120 +{{code language="cmd"}}
121 + #Add following lines
122 +
123 + # Settings apply across all Linux distros running on WSL 2
124 + [wsl2]
125 + # Limits VM memory to use no more than 4 GB, this can be set as whole numbers using GB or MB
126 + memory=16GB
127 + # Sets the VM to use two virtual processors
128 + processors=2
129 +{{/code}}
130 +
131 +
132 +**Step 7: Auto start the linux subsystem when server restarts **
128 128  
129 129  
130 130  ===3.5 Installation requirements Windows Server 2019 version 1806===
131 131  
132 -{{warning}}Please note that this section is under construction. Please contact us at productmanagement@emagiz.com{{/warning}}
137 +{{warning}}Please note that this section also applies to Windows Server 2019 version >1806{{/warning}}
133 133  
134 134  These are the requirements to allow the installation of the eMagiz Docker agent:
135 135  * Enable Hyper-V in Windows Server
... ... @@ -156,7 +156,7 @@
156 156  
157 157  ===3.6 Installation requirements Windows Server 2012 R2 ===
158 158  
159 -{{warning}}Please note that this section is under construction. Please contact us at productmanagement@emagiz.com{{/warning}}
164 +{{warning}}Please note that this section also applies to Windows Server 2019 version >1806{{/warning}}
160 160  
161 161  These are the requirements to allow the installation of the eMagiz Docker agent:
162 162  * Install & enable Hyper-V in Windows Server
... ... @@ -172,6 +172,14 @@
172 172  * Install docker as per official ubuntu documentation (See https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository) on the VM
173 173  * Go to the next section around installing the eMagiz agent
174 174  
180 +=== 3.7 eMagiz Docker agent installation ===
181 +
182 +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.
183 +
184 +[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-onpremises-installguide-deployagent.png]]
185 +
186 +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.
187 +
175 175  == 4. Assignment ==
176 176  
177 177  Check out the cheatcheet for Docker command line: