Pre-Requisites for ADCM Installation¶
ADCM requires installed Docker package on your system. Currently ADCM Docker image tested on CentOS/RHEL 7 OS.
Please check all requirements before Docker and ADCM installation
To install Docker, you need a maintained version of CentOS 7 or Alt 8 SP. Archived versions are not supported or tested.
The centos-extras repository must be enabled. This repository is enabled by default, but if you have disabled it, you need to re-enable it.
The overlay2 storage driver is recommended.
- CPU: 2-4 CPU Cores
- RAM: 8-16G
- HDD: 8-50G
Do not install upstream Docker from docker.com. Use one from official repositories of your Linux distribution. Upstream Docker tend to be unstable and less secure, than provided by your OS developer
You can install Docker in different ways, depending on your needs.
Most users set up Docker’s repositories and install from them, to ease the installation and upgrade tasks. This is the recommended approach.
Some users download the RPM-package and install it manually and manage upgrades completely manually. This is useful in situations such as installing Docker on air-gapped systems with no access to the internet.
In testing and development environments, some users choose to use automated convenience scripts to install Docker.
Install using the repository¶
Before you install Docker for the first time on a new host machine, you need to set up the Docker repository. Afterward, you can install and update Docker from the repository.
Install Necessary Packages¶
Install required packages. Yum-utils provides the yum-config-manager utility, and the device-mapper-persistent-data and lvm2 are required by the devicemapper storage driver.
sudo yum install -y yum-utils docker device-mapper-persistent-data lvm2
To start Docker:
sudo systemctl start docker
Enable docker as system service¶
To enable Docker as a system service it is necessary:
sudo systemctl enable docker
Disable Selinux (optional)¶
It is recommended SELinux to be disabled for ADCM. To temporarily disable it, run the following command on each host in your cluster:
Permanently disabling SELinux so that it does not restart on system reboot is strongly recommended. For achieving this:
vi /etc/selinux/config # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=disabled # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted