> 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/appsec-rules/iac-security/compute/appsec2-docker-1.md).

# Dockerfile contains the use of 'sudo' misconfiguration detected in code

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_DOCKER\_1                    |
| Category - Subcategory | Compute - Default Credentials Or Auth |
| Provider               | OTHER                                 |
| Severity               | LOW                                   |
| Framework              | DOCKER                                |

## Impact

Containers should be kept as lightweight and secure as possible. Installing and enabling sudo can potentially make the container more vulnerable. By default, Docker containers run as the root user, which means that sudo is not needed. Running applications within the container as a non-root user, without sudo, limits the potential damage if the application is compromised. Additionally, installing sudo increases the size of your container image. It might seem like a small addition, but for the sake of efficiency, best practices advise keeping container images as small as possible.

## How to Fix

## Since containers run commands as the root user by default, we don't need sudo to fetch the application or change its permissions. \[source,go]

FROM ubuntu:20.04

RUN apt-get update && apt-get install -y sudo curl

* RUN sudo curl -o /usr/local/bin/myapp <https://example.com/myapp> && \\
* ```
  sudo chmod +x /usr/local/bin/myapp
  ```
* RUN curl -o /tmp/myapp <https://example.com/myapp> && \\
* ```
  chmod +x /tmp/myapp && \
  ```
* ```
  mv /tmp/myapp /usr/local/bin/
  ```

## CMD \["/usr/local/bin/myapp"]


---

# 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/appsec-rules/iac-security/compute/appsec2-docker-1.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.