Changes for page Install Docker for Linux
Last modified by Erik Bakker on 2026/01/30 10:56
From version 134.1
edited by Erik Bakker
on 2026/01/23 12:52
on 2026/01/23 12:52
Change comment:
There is no comment for this version
To version 123.1
edited by Erik Bakker
on 2024/09/05 14:29
on 2024/09/05 14:29
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -18,22 +18,22 @@ 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"]]. 22 -{{/info}} 23 - 24 24 {{info}} 25 25 * Standard configuration to ensure that communication between your server and eMagiz to ensure communication. 26 26 ** registry.emagiz.com:443 27 - ** controlplane.emagiz.com:443 28 - ** controlplane-agent.emagiz.com:443 29 - ** controltower.emagiz.com:443 24 + ** controlplane.emagiz.com:8000 30 30 ** controltower.kpn-dsh.com:443 31 - ** controlbus.emagiz.com:443 32 32 ** Preferably the entry should be *.emagiz.com 33 33 ** Preferably the entry should be *.kpn-dsh.com{{/info}} 34 34 35 35 {{warning}} 36 -* When using **IP Whitelisting**, the following configuration is needed to communicate to your JMS. 30 +* In case of a very strict firewall configuration, additional configuration is needed to communicate to the eMagiz infrastructure. 31 + ** controltower.emagiz.com:443 32 + ** controltower.kpn-dsh.com:443 33 + ** controlbus.emagiz.com:443 34 + ** controlplane.emagiz.com:443 35 + 36 +* When using cloudslot number **equal to or below** 125, the following configuration is needed to communicate to your JMS. 37 37 ** 35.158.46.28:443 38 38 ** 3.74.190.88:443 39 39 ** 35.158.46.28:8443 ... ... @@ -40,15 +40,14 @@ 40 40 ** 3.74.190.88:8443 41 41 ** 35.158.46.28:8444 42 42 ** 3.74.190.88:8444 43 + 44 +* When using a cloudslot number **above** 125, the following configuration is needed to communicate to your JMS. 43 43 ** 3.74.209.20:443 44 44 ** 3.76.127.155:443 45 45 ** 3.74.209.20:8443 46 46 ** 3.76.127.155:8443 47 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}} 50 + ** 3.76.127.155:8444{{/warning}} 52 52 53 53 ===3.2 Installation Linux=== 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. ... ... @@ -77,31 +77,12 @@ 77 77 sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin 78 78 {{/code}} 79 79 80 -==== 3.2.3 Customization ==== 79 +{{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"]]. 80 +{{/info}} 81 81 82 - AfterinstallingDockeryouhave the option tostick with thestandard configuration of Docker or you can opt to altersome specific settings. One setting that can be of particular interestis the settingthat definestheIP address range yourDockerinstallationwill useto run the containers.82 +==== 3.2.3 Verify succesfull installation of the Docker Engine ==== 83 83 84 -===== 3.2.3.1 IP address range ===== 85 - 86 -Below you can find the recommended values depending on the range which can be filled in the value <ip-address> below: 87 -* 10.0.0.1/8 88 -** advised value 10.25.0.1/16 89 -* 172.16.0.1/12 90 -** advised value 172.16.0.1/16 91 -* 192.168.0.1/16 92 -** advised value 192.168.0.1/16 93 - 94 94 {{code language="cmd"}} 95 -sudo nano /etc/docker/daemon.json 96 -#Add following lines 97 -{"bip": "<ip-address>"} 98 -{{/code}} 99 - 100 -{{warning}}Be aware that the customization will only take effect once you have restarted Docker.{{/warning}} 101 - 102 -==== 3.2.4 Verify succesfull installation of the Docker Engine ==== 103 - 104 -{{code language="cmd"}} 105 105 sudo docker run hello-world 106 106 {{/code}} 107 107 ... ... @@ -109,35 +109,10 @@ 109 109 Requires ~335 Mb space to install 110 110 {{/info}} 111 111 112 -==== 3.2. 5Install eMagiz Deploy Agent ====92 +==== 3.2.4 Install eMagiz Deploy Agent ==== 113 113 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 -=== 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: 118 - 119 -{{code language="cmd"}} 120 -docker version 121 -{{/code}} 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: 124 - 125 -{{code language="cmd"}} 126 -.\install-update-docker-ce.ps1 -DockerVersion DESIRED_VERSION 127 -{{/code}} 128 - 129 -===3.4 Uninstall Docker=== 130 -To uninstall Docker from your machine, execute the following commands in PowerShell with administrative rights: 131 - 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 134 -{{/code}} 135 - 136 -Example usage: 137 - 138 -{{code language="cmd"}} 139 -.\uninstall-docker-ce.ps1 140 -{{/code}} 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