# Migrating telemetry and security agents from dockershim

Migrating telemetry and security agents from dockershimNote: This section links to third party projects that provide functionality required by Kubernetes. The Kubernetes project authors aren't responsible for these projects, which are listed alphabetically. To add a project to this list, read the content guide before submitting a change. More information.Kubernetes' support for direct integration with Docker Engine is deprecated and has been removed. Most apps do not have a direct dependency on runtime hosting containers. However, there are still a lot of telemetry and monitoring agents that have a dependency on Docker to collect containers metadata, logs, and metrics. This document aggregates information on how to detect these dependencies as well as links on how to migrate these agents to use generic tools or alternative runtimes.Telemetry and security agentsWithin a Kubernetes cluster there are a few different ways to run telemetry or security agents. Some agents have a direct dependency on Docker Engine when they run as DaemonSets or directly on nodes.Why do some telemetry agents communicate with Docker Engine?Historically, Kubernetes was written to work specifically with Docker Engine. Kubernetes took care of networking and scheduling, relying on Docker Engine for launching and running containers (within Pods) on a node. Some information that is relevant to telemetry, such as a pod name, is only available from Kubernetes components. Other data, such as container metrics, is not the responsibility of the container runtime. Early telemetry agents needed to query the container runtime and Kubernetes to report an accurate picture. Over time, Kubernetes gained the ability to support multiple runtimes, and now supports any runtime that is compatible with the container runtime interface.Some telemetry agents rely specifically on Docker Engine tooling. For example, an agent might run a command such as docker ps or docker top to list containers and processes or docker logs to receive streamed logs. If nodes in your existing cluster use Docker Engine, and you switch to a different container runtime, these commands will not work any longer.Identify DaemonSets that depend on Docker EngineIf a pod wants to make calls to the dockerd running on the node, the pod must either:mount the filesystem containing the Docker daemon's privileged socket, as a volume; ormount the specific path of the Docker daemon's privileged socket directly, also as a volume.For example: on COS images, Docker exposes its Unix domain socket at /var/run/docker.sock This means that the pod spec will include a hostPath volume mount of /var/run/docker.sock.Here's a sample shell script to find Pods that have a mount directly mapping the Docker socket. This script outputs the namespace and name of the pod. You can remove the grep '/var/run/docker.sock' to review other mounts.kubectl get pods --all-namespaces \ -o=jsonpath='{range .items[*]}{"\n"}{.metadata.namespace}{":\t"}{.metadata.name}{":\t"}{range .spec.volumes[*]}{.hostPath.path}{", "}{end}{end}' \ | sort \ | grep '/var/run/docker.sock' Note:There are alternative ways for a pod to access Docker on the host. For instance, the parent directory /var/run may be mounted instead of the full path (like in this example). The script above only detects the most common uses.Detecting Docker dependency from node agentsIf your cluster nodes are customized and install additional security and telemetry agents on the node, check with the agent vendor to verify whether it has any dependency on Docker.Telemetry and security agent vendorsThis section is intended to aggregate information about various telemetry and security agents that may have a dependency on container runtimes.We keep the work in progress version of migration instructions for various telemetry and security agent vendors in Google doc. Please contact the vendor to get up to date instructions for migrating from dockershim.Migration from dockershimAquaNo changes are needed: everything should work seamlessly on the runtime switch.DatadogHow to migrate: Docker deprecation in Kubernetes The pod that accesses Docker Engine may have a name containing any of:datadog-agentdatadogdd-agentDynatraceHow to migrate: Migrating from Docker-only to generic container metrics in DynatraceContainerd support announcement: Get automated full-stack visibility into containerd-based Kubernetes environmentsCRI-O support announcement: Get automated full-stack visibility into your CRI-O Kubernetes containers (Beta)The pod accessing Docker may have name containing:dynatrace-oneagentFalcoHow to migrate:Migrate Falco from dockershim Falco supports any CRI-compatible runtime (containerd is used in the default configuration); the documentation explains all details. The pod accessing Docker may have name containing:falcoPrisma Cloud ComputeCheck documentation for Prisma Cloud, under the "Install Prisma Cloud on a CRI (non-Docker) cluster" section. The pod accessing Docker may be named like:twistlock-defender-dsSignalFx (Splunk)The SignalFx Smart Agent (deprecated) uses several different monitors for Kubernetes including kubernetes-cluster, kubelet-stats/kubelet-metrics, and docker-container-stats. The kubelet-stats monitor was previously deprecated by the vendor, in favor of kubelet-metrics. The docker-container-stats monitor is the one affected by dockershim removal. Do not use the docker-container-stats with container runtimes other than Docker Engine.How to migrate from dockershim-dependent agent:Remove docker-container-stats from the list of configured monitors. Note, keeping this monitor enabled with non-dockershim runtime will result in incorrect metrics being reported when docker is installed on node and no metrics when docker is not installed.Enable and configure kubelet-metrics monitor.Note:The set of collected metrics will change. Review your alerting rules and dashboards.The Pod accessing Docker may be named something like:signalfx-agentYahoo Kubectl FlameFlame does not support container runtimes other than Docker. See https://github.com/yahoo/kubectl-flame/issues/51Items on this page refer to third party products or projects that provide functionality required by Kubernetes. The Kubernetes project authors aren't responsible for those third-party products or projects. See the CNCF website guidelines for more details.You should read the content guide before proposing a change that adds an extra third-party link.