Run Heartbeat on Docker

Docker images for Heartbeat are available from the Elastic Docker registry. The base image is centos:7.

A list of all published Docker images and tags is available at www.docker.elastic.co.

These images are free to use under the Elastic license. They contain open source and free commercial features and access to paid commercial features. Start a 30-day trial to try out all of the paid commercial features. See the Subscriptions page for information about Elastic license levels.

Obtaining Heartbeat for Docker is as simple as issuing a docker pull command against the Elastic Docker registry.

docker pull docker.elastic.co/beats/heartbeat:9.0.0-beta1

Alternatively, you can download other Docker images that contain only features available under the Apache 2.0 license. To download the images, go to www.docker.elastic.co.

As another option, you can use the hardened Wolfi image. Using Wolfi images requires Docker version 20.10.10 or higher. For details about why the Wolfi images have been introduced, refer to our article Reducing CVEs in Elastic container images.

docker pull docker.elastic.co/beats/heartbeat-wolfi:9.0.0-beta1

You can use the Cosign application to verify the Heartbeat Docker image signature.

wget https://artifacts.elastic.co/cosign.pub
cosign verify --key cosign.pub docker.elastic.co/beats/heartbeat:9.0.0-beta1

The cosign command prints the check results and the signature payload in JSON format:

Verification for docker.elastic.co/beats/heartbeat:9.0.0-beta1 --
The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - Existence of the claims in the transparency log was verified offline
  - The signatures were verified against the specified public key

Running Heartbeat with the setup command will create the index pattern and load visualizations and machine learning jobs. Run this command:

docker run --rm \
--cap-add=NET_RAW \
docker.elastic.co/beats/heartbeat:9.0.0-beta1 \
setup -E setup.kibana.host=kibana:5601 \
-E output.elasticsearch.hosts=["elasticsearch:9200"] <1> 12

1. Substitute your Kibana and Elasticsearch hosts and ports.
2. If you are using the hosted Elasticsearch Service in Elastic Cloud, replace the -E output.elasticsearch.hosts line with the Cloud ID and elastic password using this syntax:

-E cloud.id=<Cloud ID from Elasticsearch Service> \
-E cloud.auth=elastic:<elastic password>

If you’d like to run Heartbeat in a Docker container on a read-only file system, you can do so by specifying the --read-only option. Heartbeat requires a stateful directory to store application data, so with the --read-only option you also need to use the --mount option to specify a path to where that data can be stored.

For example:

docker run --rm \
  --mount type=bind,source=$(pwd)/data,destination=/usr/share/heartbeat/data \
  --read-only \
  docker.elastic.co/beats/heartbeat:9.0.0-beta1

The Docker image provides several methods for configuring Heartbeat. The conventional approach is to provide a configuration file via a volume mount, but it’s also possible to create a custom image with your configuration included.

Download this example configuration file as a starting point:

curl -L -O https://raw.githubusercontent.com/elastic/beats/master/deploy/docker/heartbeat.docker.yml

One way to configure Heartbeat on Docker is to provide heartbeat.docker.yml via a volume mount. With docker run, the volume mount can be specified like this.

docker run -d \
  --name=heartbeat \
  --user=heartbeat \
  --volume="$(pwd)/heartbeat.docker.yml:/usr/share/heartbeat/heartbeat.yml:ro" \
  --cap-add=NET_RAW \
  docker.elastic.co/beats/heartbeat:9.0.0-beta1 \
  --strict.perms=false -e \
  -E output.elasticsearch.hosts=["elasticsearch:9200"] <1> 12

1. Substitute your Elasticsearch hosts and ports.
2. If you are using the hosted Elasticsearch Service in Elastic Cloud, replace the -E output.elasticsearch.hosts line with the Cloud ID and elastic password using the syntax shown earlier.

The heartbeat.docker.yml downloaded earlier should be customized for your environment. See Configure for more details. Edit the configuration file and customize it to match your environment then re-deploy your Heartbeat container.

It’s possible to embed your Heartbeat configuration in a custom image. Here is an example Dockerfile to achieve this:

FROM docker.elastic.co/beats/heartbeat:9.0.0-beta1
COPY --chown=root:heartbeat heartbeat.yml /usr/share/heartbeat/heartbeat.yml

Under Docker, Heartbeat runs as a non-root user, but requires some privileged network capabilities to operate correctly. Ensure that the NET_RAW capability is available to the container.

docker run --cap-add=NET_RAW docker.elastic.co/beats/heartbeat:9.0.0-beta1