Customizing for container services (Docker)

Use these instructions if you want to customize your deployment to use the container services (Docker) topology.

Before you begin

Table 1. Summary of support details
Support Options	Details
Support for post-deployment customization?	No
Supported topologies?	All, except Minimal topology
Operating system?	Red Hat Enterprise Linux 7.1
Architecture?	x64

Notes:

If you need to deploy the container services feature without an Internet connection, see the Container services (Docker) prerequisites topic for specific prerequisites. This only applies if there is no Internet connection.
Before configuring container services, you can review Limitations for Container services (Docker) in IBM Cloud Manager with OpenStack.
If you are not using the Platform Resource Scheduler (PRS), you do not need to change the controller node roles that are related to Docker customization.

Procedure

Append the following container services roles to the run list for the single controller and the Docker container node as follows:

Single controller and Docker container node

Table 2. Container service roles
Node type	Run list
Controller	Use the ibm-os-docker-controller-node role to make a controller node that supports Docker compute nodes. This role is mutually exclusive to ibm-os-single-controller-node in a runlist. For example: `role[ibm-os-docker-controller-node] role[ibm-os-prs-ego-master] role[ibm-os-prs-controller-node] role[ibm-sce-node]`
Docker compute node	Use the ibm-os-docker-compute-node-kvm role to make a Docker compute node. This role is mutually exclusive to ibm-os-compute-node-kvm in a runlist. For example: `role[ibm-os-docker-compute-node-kvm] role[ibm-os-prs-compute-node]` Note: This role adds Docker support on top of ibm-os-compute-node-kvm. There is no support for Power Systems.

High Availability (HA) controller node and Docker container node

Table 3. Container service roles
Node type	Run list
High Availability (HA) Controller	With a HA controller, there are no specific role changes required for Docker customization. Use the default values. For example: `role[ibm-os-ha-controller-node]`
Docker compute node	Use the ibm-os-docker-compute-node-kvm role to make a Docker compute node. This role is mutually exclusive to ibm-os-compute-node-kvm in a runlist. For example: `role[ibm-os-docker-compute-node-kvm]`

Note: If you are using mixed (both KVM and Docker) compute nodes in the same cloud, use the controller runlist as previously referenced. However, use the Docker compute runlist only for Docker compute nodes in the cloud.

To finish the customization, return to the relevant topology deployment process and complete the remaining steps.
Important: If installation of the cloud fails at "install cadvisor", then you must restart the Docker service on the compute node (service docker restart command) and redeploy the cloud.