> 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-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/automation/engines/install-an-engine/docker/docker-hardening-guide/run-docker-with-non-root-internal-users.md).

# Run Docker with non-root internal users

Run Docker containers with non-root internal users.

For additional security isolation, we recommend to run Docker containers as non-root internal users. This follows the principle of least privilege.

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-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/automation/engines/configure-engines.md).
2. Add the following key:

   **`"docker.run.internal.asuser": true`**
3. For containers that do not support non-root internal users, add the following key:

   **`"docker.run.internal.asuser.ignore" : "`*****`A comma separated list of container names. The engine matches the container names according to the prefixes of the key values>`*****`"`**

   For example, **`"docker.run.internal.asuser.ignore"="demisto/python3:","demisto/python:"`**

   The engine matches the key values for the following containers:

   ```
   demisto/python:1.3-alpine
   demisto/python:2.7.16.373
   demisto/python3:3.7.3.928
   demisto/python3:3.7.4.977
   ```

   The **`:`** character should be used to limit the match to the full name of the container. For example, using the **`:`** character does not find **`demisto/python-ubuntu:2.7.16.373`**.
4. Save the changes.
5. 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-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/automation/engines/install-an-engine/docker/docker-hardening-guide/run-docker-with-non-root-internal-users.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.