WARNING: Version 5.5 of Packetbeat 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 Packetbeat are available from the Elastic Docker
registry. You can retrieve an image with a
docker pull command.
docker pull docker.elastic.co/beats/packetbeat:5.5.3
Configuring Packetbeat on Dockeredit
The Docker image provides several methods for configuring Packetbeat. 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 Packetbeat on Docker is to provide
packetbeat.yml via bind-mounting.
docker run, the bind-mount can be specified like this:
docker run \ -v ~/packetbeat.yml:/usr/share/packetbeat/packetbeat.yml \ docker.elastic.co/beats/packetbeat:5.5.3
Custom Image Configurationedit
It’s possible to embed your Packetbeat configuration in a custom image. Here is an example Dockerfile to achieve this:
FROM docker.elastic.co/beats/packetbeat:5.5.3 COPY packetbeat.yml /usr/share/packetbeat/packetbeat.yml USER root RUN chown packetbeat /usr/share/packetbeat/packetbeat.yml USER packetbeat