Install Docker for Linux

Last modified by Carlijn Kokkeler on 2024/03/28 11:01

In this microlearning, we will focus on how an on-premises server can be prepared for a eMagiz Deploy agent installation.

Should you have any questions, please contact academy@emagiz.com.

1. Prerequisites

  • Advanced knowledge of the eMagiz platform
  • Good understanding of eMagiz runtimes in general

2. Key concepts

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.
 
In the below section the Linux variant is described in terms of how to prepare the server to allow the eMagiz Deploy Agent to be installed. That agent allows to download images from the eMagiz infrastructure.
  

3. On-premises deployments

3.1 General requirements

These are the general requirements to allow the installation of the eMagiz Docker agent:

  • Standard configuration to ensure that communication between your server and eMagiz to ensure communication.
    • registry.emagiz.com:443
    • controlplane.emagiz.com:8000
    • controltower.kpn-dsh.com:443
    • Preferably the entry should be *.emagiz.com
    • Preferably the entry should be *.kpn-dsh.com
  • In case of a very strict firewall configuration, additional configuration is needed to communicate to the eMagiz infrastructure.
    • controltower.emagiz.com:443
    • controltower.kpn-dsh.com:443
    • controlbus.emagiz.com:443
    • controlplane.emagiz.com:443
  • When using cloudslot number equal to or below 125, the following configuration is needed to communicate to your JMS.
    • 35.158.46.28:443
    • 3.74.190.88:443
    • 35.158.46.28:8443
    • 3.74.190.88:8443
    • 35.158.46.28:8444
    • 3.74.190.88:8444
  • When using a cloudslot number above 125, the following configuration is needed to communicate to your JMS.
    • 3.74.209.20:443
    • 3.76.127.155:443
    • 3.74.209.20:8443
    • 3.76.127.155:8443
    • 3.74.209.20:8444
    • 3.76.127.155:8444

3.2 Installation Linux

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.

3.2.1 Set up Docker's apt repository

# Add Docker's official GPG key:
sudo apt-get update
sudo apt-get install ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc

# Add the repository to Apt sources:
echo \
  "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \
  $(. /etc/os-release && echo "$VERSION_CODENAME") stable" | \
  sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt-get update

3.2.2 Install Docker

sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

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.

3.2.3 Verify succesfull installation of the Docker Engine

sudo docker run hello-world

 Requires 335 Mb space to install

3.2.4 Install eMagiz Deploy Agent

Install the eMagiz Deploy agent as can be found in this microlearning

4. Key takeaways

  • 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
  • eMagiz has a specific agent that manages the download of that image to the on-premises server
  • 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.

5. Suggested Additional Readings