---
title: The Docker instance should not use devicemapper as its storage driver
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > Datadog Security > OOTB Rules > The Docker instance should not use
  devicemapper as its storage driver
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# The Docker instance should not use devicemapper as its storage driver
Classification:complianceFramework:cis-dockerControl:2.7 
## Description{% #description %}

Docker should use a storage driver other than `devicemapper`.

## Rationale{% #rationale %}

The devicemapper driver is deprecated, Docker 25 removed it, and its loop-lvm mode suits only testing.

## Audit{% #audit %}

Show the storage driver of the daemon:

```bash
docker info --format 'Storage Driver: {{ .Driver }}'
```

Datadog passes the rule when the storage driver is other than `devicemapper` and fails it otherwise.

## Remediation{% #remediation %}

Choose a supported storage driver, such as `overlay2` or the containerd snapshotter, with `storage-driver` in `daemon.json` or `--storage-driver`. Changing the driver hides the images and containers of the old one.

## Impact{% #impact %}

Containers and images of the old driver need to be recreated.

## Default value{% #default-value %}

Docker picks a supported driver, `overlayfs` with the containerd image store of Docker 29.

## References{% #references %}

1. [https://docs.docker.com/engine/storage/drivers/select-storage-driver/](https://docs.docker.com/engine/storage/drivers/select-storage-driver/)
