Changes for page Install Docker for Linux
Last modified by Erik Bakker on 2026/04/21 12:16
From version 143.1
edited by Erik Bakker
on 2026/04/21 12:05
on 2026/04/21 12:05
Change comment:
There is no comment for this version
To version 135.1
edited by Erik Bakker
on 2026/01/23 13:00
on 2026/01/23 13:00
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
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 2 9.1.3as 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 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 22 {{/info}} 23 23 24 24 {{info}} ... ... @@ -29,16 +29,11 @@ 29 29 ** controltower.emagiz.com:443 30 30 ** controltower.kpn-dsh.com:443 31 31 ** controlbus.emagiz.com:443 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}} 32 + ** Preferably the entry should be *.emagiz.com 33 + ** Preferably the entry should be *.kpn-dsh.com{{/info}} 38 38 39 39 {{warning}} 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 - 36 +* When using **IP Whitelisting**, the following configuration is needed to communicate to your JMS. 42 42 ** 35.158.46.28:443 43 43 ** 3.74.190.88:443 44 44 ** 35.158.46.28:8443 ... ... @@ -99,7 +99,6 @@ 99 99 {{/code}} 100 100 101 101 Select the desired version and install: 102 - 103 103 {{code language="cmd"}} 104 104 VERSION_STRING=5:29.1.5-1~ubuntu.24.04~noble 105 105 sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin ... ... @@ -149,7 +149,8 @@ 149 149 150 150 docker-ce/noble 5:29.1.5-1~ubuntu.24.04~noble <arch> 151 151 docker-ce/noble 5:29.1.4-1~ubuntu.24.04~noble <arch> 152 -...{{/code}} 146 +... 147 +{{/code}} 153 153 154 154 Select the desired version and install. 155 155 ... ... @@ -158,8 +158,6 @@ 158 158 sudo apt install docker-ce=$VERSION_STRING docker-ce-cli=$VERSION_STRING containerd.io docker-buildx-plugin docker-compose-plugin 159 159 {{/code}} 160 160 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 - 163 163 ===3.4 Uninstall Docker=== 164 164 To uninstall Docker from your machine, execute the following command. 165 165 ... ... @@ -168,7 +168,7 @@ 168 168 {{/code}} 169 169 170 170 {{warning}}Images, containers, volumes, or custom configuration files on your host aren't automatically removed. To delete all images, containers, and volumes: 171 - 164 + 172 172 {{code language="cmd"}} 173 173 sudo rm -rf /var/lib/docker 174 174 sudo rm -rf /var/lib/containerd