Before configuring a Docker bundle in Pacemaker, the user must install Docker and supply a fully configured Docker image on every node allowed to run the bundle.
Pacemaker will create an implicit ocf:heartbeat:docker
resource to manage a bundle’s Docker container. The user must ensure that resource agent is installed on every node allowed to run the bundle.
Table 9.11. Properties of a Bundle’s Docker Element
Field
|
Default
|
Description
|
---|
image
|
|
Docker image tag (required)
|
replicas
|
Value of promoted-max if that is positive, else 1
|
A positive integer specifying the number of container instances to launch
|
replicas-per-host
|
1
|
A positive integer specifying the number of container instances allowed to run on a single node
|
promoted-max
|
0
|
A non-negative integer that, if positive, indicates that the containerized service should be treated as a promotable service, with this many replicas allowed to run the service in the master role
|
network
|
|
If specified, this will be passed to docker run as the network setting for the Docker container.
|
run-command
|
/usr/sbin/pacemaker-remoted if bundle contains a primitive , otherwise none
|
This command will be run inside the container when launching it ("PID 1"). If the bundle contains a primitive , this command must start pacemaker-remoted (but could, for example, be a script that does other stuff, too). If the container image has a pre-2.0.0 version of Pacemaker, set this to /usr/sbin/pacemaker_remoted (note the underbar instead of dash).
|
options
|
|
Extra command-line options to pass to docker run
|
For backward compatibility, masters
is accepted as an alias for promoted-max
, but is deprecated since 2.0.0, and support for it will be removed in a future version.