> 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-agentix/configure-cortex-agentix/engines/docker/docker-hardening-guide/configure-the-memory-limit-support-without-swap-capabilities.md).

# Configure the memory limit support without swap capabilities

Configure Docker memory limits without swap support for Cortex AgentiX engines.

When a container exceeds the specified amount of memory, the container starts to swap. Not all Linux distributions have the swap limit support enabled by default.

* Red Hat distributions usually have swap limit support enabled by default.
* Ubuntu distributions usually have swap limit support disabled by default.

To protect the host from a container using too many system resources (either because of a software bug or a DoS attack), limit the resources available for each container. In the engine configuration file, some of these settings are set using the advanced parameter: **`python.pass.extra.keys`**. This key receives as a parameter full **`docker run`** options, separated with the **`##`** string.

How to check if your system supports swap limit capabilities

1. On the engine machine, run the following command:

   **`sudo docker run --rm -it --memory=1g demisto/python:1.3-alpine true`**
2. If **`swap limit capabilities`** is enabled, [configure the memory limitation](/cortex-agentix/configure-cortex-agentix/engines/docker/docker-hardening-guide/configure-the-memory-limitation.md). To test the memory, see step 5 of [configure the memory limitation](/cortex-agentix/configure-cortex-agentix/engines/docker/docker-hardening-guide/configure-the-memory-limitation.md).
3. If you see the following message in the output (the message may vary between Docker versions):

   **`WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.`**

   You have 2 options:

   * Configure **`swap limit capabilities`** by following the [Docker documentation](https://docs.docker.com/config/containers/resource_constraints/).
   * See [how to configure memory limit support without swap capabilities](/cortex-agentix/configure-cortex-agentix/engines/docker/docker-hardening-guide/configure-the-memory-limit-support-without-swap-capabilities.md).

   If you see the **`WARNING: No swap limit support`** you can configure memory support without swap limit capabilities.

How to configure the memory limit support without swap limit capabilities

1. Edit the engine configuration file either by editing the `d1.conf` file, or If you installed via Shell, you can edit the configuration in the UI as well as editing the file directly. For details, see [Configure engines](/cortex-agentix/configure-cortex-agentix/engines/configure-engines.md).
2. Add the following key to disable swap memory enforcement:

   **`"python.pass.extra.keys": "--memory=1g##--memory-swap=-1"`**

   If you have the **`python.pass.extra.keys`** already set up with a value, add the value after the **`##`** separator.
3. Save the changes.
4. Restart the demisto service on the engine machine.

   **`sudo systemctl start d1`**

   (Ubuntu) **`sudo service d1 restart`**


---

# 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://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/engines/docker/docker-hardening-guide/configure-the-memory-limit-support-without-swap-capabilities.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.