> 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-i-allocate-more-storage-to-root-filesystem-of-a-pod.md).

# Procedure to Allocate More Storage to Root Filesystem of a Pod

## Problem

* Is it possible to Allocate more storage to the Root Filesystem of a pod?
* How to increase the current root filesystem size for a pod?

## Environment

* Platform9 Managed Kubernetes - All Versions
* Docker Storage Driver - DeviceMapper

## Answer

* For the cluster setups with DeviceMapper as the Docker Storage Driver, the docker configuration decides the size of container or pod root filesystem.
* The parameter `Base Device Size` in docker configuration decides the size of each LVM Logical Volume that will be carved from the total backend Storage Space configured for the Docker Storage.
* This Logical Volume then acts as backend disk for the pod or container.
* To change this parameter we need to change the value of this parameter but there are few caveats. This will be an independent change in docker daemon on each cluster node and this might not be consistent across the docker upgrades performed during the cluster upgrade.
* Hence it is advisable to stick to the default size of a pod root filesystem rather than increasing it by allocating more space.


---

# 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-i-allocate-more-storage-to-root-filesystem-of-a-pod.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.