> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/configure-cortex-xsoar/engines/install-an-engine/podman/change-container-storage-directory.md).

# Change container storage directory

By default, Podman uses the **`$HOME/.local/share/containers/storage`** directory. To use a different directory for container storage, edit the [Podman config file](https://github.com/containers/podman/blob/main/vendor/github.com/containers/storage/storage.conf#L33) located at **`/home/demisto/.config/containers/storage.conf`**. If the Podman config file does not exist, you need to create it and change the ownership.

The new storage directory needs to be owned by the **demisto** user, otherwise they will be denied access to it.

{% hint style="warning" %}

### Warning

Do not use NAS storage or a temporary (tmpfs) directory for the **`graphroot`** setting. The **`graphroot`** needs to be a local, non-temporary directory for Podman to work. For more information, see <https://en.wikipedia.org/wiki/Network-attached_storage>.
{% endhint %}

{% hint style="info" %}

### Tip

We recommend reserving 150 GB for container storage, either in the /home partition or a different storage directory that you have set using the **`grarphroot`** key.
{% endhint %}

1. If the Podman config file does not exist:
   1. Create the Podman config file.

      **`sudo mkdir -p /home/demisto/.config/containers`**

      **`cp /etc/containers/storage.conf /home/demisto/.config/containers`**
   2. Change the ownership of the Podman config file.

      **`sudo chown -R demisto:demisto /home/demisto`**
2. To set a different directory for container storage, change the key: **`graphroot`** in the **`storage.conf`** file. For example:

   **`graphroot = "/var/lib/containers/xsoar-storage"`**
3. Some additional changes are required in the storage.conf file. Comment out the **`runroot`** setting by adding a **`#`** (hash) before it. For example:

   **`#runroot = "/run/containers/storage"`**

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Alternatively, the <strong><code>runroot</code></strong> setting may be set to some temporary directory that is accessible by user demisto. If you choose to set the <strong><code>runroot</code></strong>, it must be a directory that is mounted as tmpfs (temporary filesystem), unlike the graphroot.</p></div>
4. Under \[storage.options.overlay], uncomment the following line (remove the # from the start):

   **`mount_program = "/usr/bin/fuse-overlayfs"`**
5. If the engine has already been installed, apply your changes to any existing containers:

   **`sudo -u demisto podman system migrate`**
6. Verify the change (once the engine is installed):

   **`sudo -u demisto podman info | grep graph`**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.12/configure-cortex-xsoar/engines/install-an-engine/podman/change-container-storage-directory.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.