Skip to content

Tracee Events Container Enrichment

Tracee events provide context about where the collected events originated from, including information about the originating container if available. To gather this information, Tracee needs to communicate with the relevant container runtime.

Detecting container runtime

Tracee will automatically search for known supported runtimes by looking for their socket files in known locations.
You may track if Tracee was able to find the container runtime socket by running Tracee with debug log level. There will be a line to each known runtime engine socket and a message sharing it's status.

When running Tracee in a container, the runtime sockets must be mounted to be available for Tracee.

For example, if running Tracee using Docker, and ContainerD runtime:

docker run --name tracee -it --rm \
  --pid=host --cgroupns=host --privileged \
  -v /etc/os-release:/etc/os-release-host:ro \
  -v /var/run/containerd:/var/run/containerd:ro \

Most container runtimes have their sockets installed by default in /var/run, so mounting this path can also be a good option.

Supported Container Runtime Engines

Tracee supports the following container runtimes and will look in the following paths for their socket files:

  1. Docker: /var/run/docker.sock
  2. Containerd: /var/run/containerd/containerd.sock
  3. CRI-O: /var/run/crio/crio.sock
  4. Podman: /var/run/podman/podman.sock