WARNING: Version 6.0 of Auditbeat 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.
Docker images for Auditbeat are available from the Elastic Docker
registry. You can retrieve an image with a
docker pull command.
docker pull docker.elastic.co/beats/auditbeat:6.0.1
Configure Auditbeat on Dockeredit
The Docker image provides several methods for configuring Auditbeat. 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.
One way to configure Auditbeat on Docker is to provide
auditbeat.yml via bind-mounting.
docker run, the bind-mount can be specified like this:
docker run \ -v ~/auditbeat.yml:/usr/share/auditbeat/auditbeat.yml \ docker.elastic.co/beats/auditbeat:6.0.1
Custom image configurationedit
It’s possible to embed your Auditbeat configuration in a custom image. Here is an example Dockerfile to achieve this:
FROM docker.elastic.co/beats/auditbeat:6.0.1 COPY auditbeat.yml /usr/share/auditbeat/auditbeat.yml USER root RUN chown auditbeat /usr/share/auditbeat/auditbeat.yml USER auditbeat
Under Docker, Auditbeat runs as a non-root user, but requires some privileged
capabilities to operate correctly. Ensure that the
capabilities are available to the container.
It is also essential to run Auditbeat in the host PID namespace.
docker run --cap-add=AUDIT_CONTROL,AUDIT_READ --pid=host docker.elastic.co/beats/auditbeat:6.0.1