docker source

Ingests data through the docker engine daemon and outputs `log` events.

The docker source is in beta. Please see the current enhancements and bugs for known issues. We kindly ask that you add any missing issues as it will help shape the roadmap of this component.

The docker source ingests data through the docker engine daemon and outputs log events.

Config File

vector.toml (simple)
vector.toml (advanced)
[sources.my_source_id]
type = "docker" # must be: "docker"
# For a complete list of options see the "advanced" tab above.

Options

Key

Type

Description

REQUIRED

type

string

The component type required must be: "docker"

OPTIONAL

include_containers

[string]

A list of container ids to match against when filtering running containers. This will attempt to match the container id from the beginning meaning you do not need to include the whole id but just the first few characters. If no containers ids are provided, all containers will be included. no default example: "ffd2bc2cb74a"

include_labels

[string]

A list of container object labels to match against when filtering running containers. This should follow the described label's synatx in docker object labels docs. no default example: "key=value"

How It Works

Connecting to the Docker daemon

Vector will automatically attempt to connect to the docker daemon for you. In most situations if your current user is able to run docker ps then Vector will be able to connect. Vector will also respect if DOCKER_HOST and DOCKER_VERIFY_TLS are set. Vector will also use the other default docker environment variables if they are set. See the Docker daemon docs.

Delivery Guarantee

Due to the nature of this component, it offers a best effort delivery guarantee.

Environment Variables

Environment variables are supported through all of Vector's configuration. Simply add ${MY_ENV_VAR} in your Vector configuration file and the variable will be replaced before being evaluated.

You can learn more in the Environment Variables section.

Troubleshooting

The best place to start with troubleshooting is to check the Vector logs. This is typically located at /var/log/vector.log, then proceed to follow the Troubleshooting Guide.

If the Troubleshooting Guide does not resolve your issue, please:

  1. If encountered a bug, please file a bug report.

  2. If encountered a missing feature, please file a feature request.

  3. If you need help, join our chat/forum community. You can post a question and search previous questions.

Resources