> 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/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/podman/podman-installation.md).

# Podman Installation

Install Podman for Cortex XSOAR 6.14 on supported Linux operating systems.

When installing a new server or engine on RHEL 8 or later, the shell installer configures Podman automatically. There are some cases, however, where you might need to install Podman manually:

* When using an installation method other than the shell installer (e.g. an RPM package) on RHEL 8 or later.
* When the shell installer did not successfully install Podman.
* When you want to migrate from Docker to Podman, for an existing Cortex XSOAR server or engine.

{% hint style="info" %}

* This procedure is intended for RHEL 8 or later. It may not work for other operating system types.
* Do not use [NAS storage](https://en.wikipedia.org/wiki/Network-attached_storage) for the $HOME directory. The directory needs to be a local directory for Podman to work.
  {% endhint %}

1. For RHEL 8, install Podman by typing the following commands:

   * `sudo yum -y install slirp4netns fuse-overlayfs`
   * `sudo yum -y module install container-tools`

   For RHEL 9 or later, install Podman by typing the following command:

   * `sudo yum -y install slirp4netns fuse-overlayfs podman`
2. Run the following commands:
   * `sudo touch /etc/subuid /etc/subgid`
   * `sudo mkdir -p /home/demisto`
   * `sudo chown demisto:demisto /home/demisto`
3. Configure the `unqualified-search-registries` used by Podman.

   Podman by default uses the fedoraproject.org, redhat.com, and docker.io unqualified search registries. Since Cortex XSOAR images use only the docker.io registry, you can speed up download times for container images by setting `unqualified-search-registries` to just docker.io.

   1. Create or edit the `/home/demisto/.config/containers/registries.conf` config file.
   2. In the file, set the following:

      `unqualified-search-registries = ['docker.io']`

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>If you edit the file with the <code>root</code> user, make sure to set the <code>demisto</code> user as file owner by running <code>chown demisto:demisto /home/demisto/.config/containers/registries.conf</code></p></div>
4. Change the `subuids` and `subgids` by running the following command:

   `sudo usermod --add-subuids 200000-265535 --add-subgids 200000-265535 demisto`
5. Migrate existing containers to Podman by typing the following command:

   `sudo sh -c "cd /; runuser -u demisto -- podman system migrate"`
6. Set the `net.ipv4.ping-group-range`, by typing the following commands:
   * `sudo sh -c "echo 'net.ipv4.ping_group_range=0 2000000' > /etc/sysctl.d/demisto-ping.conf"`
   * `sudo sysctl -w "net.ipv4.ping_group_range=0 2000000"`
7. As root user, edit one of the following `config` files:
   * Server:

     `/etc/demisto.conf`
   * Engine:

     `/usr/local/demisto/d1.conf`
8. Change the `"container.engine.type": "docker"` to `"podman"`.

   If this line does not exist, add the following line to the file:

   `"container.engine.type": "podman"`

   ```programlisting
      "Server": {
                   "HttpsPort": "443",
                   "ProxyMode": true
           },
           "container": {
                                   "engine": {
                                           "type": "podman"
                                   }
           },
           "db": {
                   "index": {
                           "entry": {
                                   "disable": true
   ```
9. If the engine or server is running, restart the service.
   * Server: `sudo systemctl restart demisto`
   * Engine: `sudo systemctl restart d1`


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/podman/podman-installation.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 `build a script that syncs our docs to a CMS` 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.