Changes for page Install Docker for Linux

Last modified by Erik Bakker on 2026/04/21 12:16

From version 134.1
edited by Erik Bakker
on 2026/01/23 12:52
Change comment: There is no comment for this version
To version 143.1
edited by Erik Bakker
on 2026/04/21 12:05
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,7 +18,7 @@
18 18  ===3.1 General requirements===
19 19  These are the general requirements to allow the installation of the eMagiz Docker agent:
20 20  
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"]].
21 +{{info}}It is advised to use Docker version 29.1.3 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 22  {{/info}}
23 23  
24 24  {{info}}
... ... @@ -29,11 +29,16 @@
29 29   ** controltower.emagiz.com:443
30 30   ** controltower.kpn-dsh.com:443
31 31   ** controlbus.emagiz.com:443
32 - ** Preferably the entry should be *.emagiz.com
33 - ** Preferably the entry should be *.kpn-dsh.com{{/info}}
32 + ** {yourcloudslotid}.emagizcloud.com:8443
33 +
34 +* Preferably we suggest to implement the following entries on DNS level.
35 + ** *.emagizcloud.com
36 + ** *.emagiz.com
37 + ** *.kpn-dsh.com{{/info}}
34 34  
35 35  {{warning}}
36 -* When using **IP Whitelisting**, the following configuration is needed to communicate to your JMS.
40 +* When **your** requirements force the use of **IP Whitelisting**, the following configuration is needed to communicate with our infrastructure and the specific eMagiz model(s) to which you need to connect. These IP addresses are subject to periodic change on our end.
41 +
37 37   ** 35.158.46.28:443
38 38   ** 3.74.190.88:443
39 39   ** 35.158.46.28:8443
... ... @@ -51,8 +51,18 @@
51 51   ** 3.123.136.31{{/warning}}
52 52  
53 53  ===3.2 Installation Linux===
59 +
54 54  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.
55 55  
62 +==== 3.2.1 Uninstall old versions ====
63 +{{info}}Before you can install Docker Engine, you need to uninstall any conflicting packages.
64 +
65 +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}}
66 +
67 +{{code language="cmd"}}
68 +sudo apt remove $(dpkg --get-selections docker.io docker-compose docker-compose-v2 docker-doc podman-docker containerd runc | cut -f1)
69 +{{/code}}
70 +
56 56  ==== 3.2.1 Set up Docker's apt repository ====
57 57  
58 58  {{code language="cmd"}}
... ... @@ -73,10 +73,23 @@
73 73  
74 74  ==== 3.2.2 Install Docker ====
75 75  
91 +To install a specific version of Docker Engine, start by listing the available versions in the repository:
92 +
76 76  {{code language="cmd"}}
77 -sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
94 +apt list --all-versions docker-ce
95 +
96 +docker-ce/noble 5:29.1.5-1~ubuntu.24.04~noble <arch>
97 +docker-ce/noble 5:29.1.4-1~ubuntu.24.04~noble <arch>
98 +...
78 78  {{/code}}
79 79  
101 +Select the desired version and install:
102 +
103 +{{code language="cmd"}}
104 +VERSION_STRING=5:29.1.5-1~ubuntu.24.04~noble
105 +sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin
106 +{{/code}}
107 +
80 80  ==== 3.2.3 Customization ====
81 81  
82 82  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.
... ... @@ -114,30 +114,44 @@
114 114  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"]]
115 115  
116 116  === 3.3 Update Docker ===
117 -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:
145 +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:
118 118  
119 119  {{code language="cmd"}}
120 -docker version
121 -{{/code}}
148 +apt list --all-versions docker-ce
122 122  
123 -When this returns a version **lower** than the advised version shown under the "General requirements" section, you can update Docker on your machine. To do so, execute the following command in PowerShell with administrative rights:
150 +docker-ce/noble 5:29.1.5-1~ubuntu.24.04~noble <arch>
151 +docker-ce/noble 5:29.1.4-1~ubuntu.24.04~noble <arch>
152 +...{{/code}}
124 124  
154 +Select the desired version and install.
155 +
125 125  {{code language="cmd"}}
126 -.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION
157 +VERSION_STRING=5:29.1.5-1~ubuntu.24.04~noble
158 +sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin
127 127  {{/code}}
128 128  
161 +{{warning}}It may happen that, due to the update, your containers are no longer starting up. To resolve this, please restart the containers, which can be done via a deployment plan or the deploy architecture.{{/warning}}
162 +
129 129  ===3.4 Uninstall Docker===
130 -To uninstall Docker from your machine, execute the following commands in PowerShell with administrative rights:
164 +To uninstall Docker from your machine, execute the following command.
131 131  
132 132  {{code language="cmd"}}
133 -Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/emagiz/windows-support/main/Uninstall-docker/uninstall-docker.ps1" -o uninstall-docker-ce.ps1
167 +sudo apt purge docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin docker-ce-rootless-extras
134 134  {{/code}}
135 135  
136 -Example usage:
170 +{{warning}}Images, containers, volumes, or custom configuration files on your host aren't automatically removed. To delete all images, containers, and volumes:
137 137  
138 138  {{code language="cmd"}}
139 -.\uninstall-docker-ce.ps1
173 +sudo rm -rf /var/lib/docker
174 +sudo rm -rf /var/lib/containerd
175 +Remove source list and keyrings
140 140  {{/code}}
177 +
178 +{{code language="cmd"}}
179 + sudo rm /etc/apt/sources.list.d/docker.sources
180 + sudo rm /etc/apt/keyrings/docker.asc
181 +{{/code}}
182 +{{/warning}}
141 141  == 4. Key takeaways ==
142 142  
143 143  * 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