WARNING: Version 6.1 of Heartbeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Running Heartbeat on Docker
editRunning Heartbeat on Docker
editDocker images for Heartbeat are available from the Elastic Docker
registry. You can retrieve an image with a docker pull command.
docker pull docker.elastic.co/beats/heartbeat:6.1.4
The base image is centos:7 and the source code can be found on GitHub.
Configure Heartbeat on Docker
editThe Docker image provides several methods for configuring Heartbeat. The conventional approach is to provide a configuration file via a bind-mounted volume, but it’s also possible to create a custom image with your configuration included.
Bind-mounted configuration
editOne way to configure Heartbeat on Docker is to provide heartbeat.yml via bind-mounting.
With docker run, the bind-mount can be specified like this:
docker run \ -v ~/heartbeat.yml:/usr/share/heartbeat/heartbeat.yml \ docker.elastic.co/beats/heartbeat:6.1.4
Custom image configuration
editIt’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:6.1.4 COPY heartbeat.yml /usr/share/heartbeat/heartbeat.yml USER root RUN chown heartbeat /usr/share/heartbeat/heartbeat.yml USER heartbeat