> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/frequently-asked-questions/can-we-use-docker-storage-driver-in-loop-lvm-mode-for-our-cluste.md).

# Can we use Docker Storage Driver in loop-lvm Mode on PMK Cluster?

## Problem

* Is it possible to setup the PMK cluster with docker storage driver in `loop-lvm` mode and are there any concerns related to it?

## Environment

* Platform9 Managed Kubernetes - All Versions
* Docker

## Answer

* For production setups, the device-mapper docker storage driver must be configured to use `direct-lvm` mode.
* The `loop-lvm` mode is acceptable only for testing but is **not supported for production deployments.**
* Frequently `loop-lvm` mode is preferred over the `direct-lvm` mode in non-production or testing setups because unlike direct-lvm, it does not need `one free block device (a disk or a partition)` on the node.
* Although with `loop-lvm` there is a common and known issue where the the Docker storage gets filled up more frequently due to failure in deletion of the old unwanted data.
* The remedy to this is pruning the docker data manually using the below mentioned command.

{% tabs %}
{% tab title="Command to prune Docker data" %}

```javascript
# docker system prune -a -f --volumes
```

{% endtab %}
{% endtabs %}

* There is one more and **most recommended approach** which is to use the `Overlay2` as the Docker storage driver in production environment since it is more stable that `device-mapper`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmk/frequently-asked-questions/can-we-use-docker-storage-driver-in-loop-lvm-mode-for-our-cluste.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.