> 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/appsec-docker-2.md).

# Healthcheck instructions have not been added to container images misconfiguration detected in code

## Rule Details

|                        |                                         |
| ---------------------- | --------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_DOCKER\_2                       |
| Category - Subcategory | Compute - Unsanctioned Resource Or Type |
| Provider               | OTHER                                   |
| Severity               | LOW                                     |
| Framework              | DOCKER                                  |

## Impact

This rule detects whether HEALTHCHECK instructions have been added to Docker container images. These instructions provide a way to check the health of the running container, ensuring that issues are detected and handled promptly, improving the reliability and stability of your containerized applications. Adding HEALTHCHECK instructions to your Dockerfiles follows best practices for Docker container health management.

## How to Fix

To mitigate this issue, add HEALTHCHECK instructions to your Dockerfile. Define a command that will be used to check the health of the container and specify the interval, timeout, and retries for how often the check should be performed.

## Example: \[source,go]

* HEALTHCHECK --interval=30s --timeout=3s --retries=3 CMD curl -f <http://localhost/health> || exit 1

***


---

# 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/appsec-docker-2.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.