> For the complete documentation index, see [llms.txt](https://docs.konvu.com/konvu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konvu.com/konvu/triage-and-remediation/finding-types/containers.md).

# Containers

How Konvu assesses vulnerabilities in your container images. Beta, available with the container add-on.

A container finding says an OS package in one of your images has a known vulnerability. Many depend on conditions the image never meets: a service that is not running, a configuration that is not set. Konvu checks each finding against the image and tells you which ones apply.

{% hint style="info" %}
Container triage is in beta and requires the container add-on. Contact your Konvu team to enable it.
{% endhint %}

|                        |                                                                                        |
| ---------------------- | -------------------------------------------------------------------------------------- |
| **Sources**            | AWS Inspector (including Amazon ECR basic scanning), Wiz, Snyk Container               |
| **Where to find them** | **Triage > Container**                                                                 |
| **Assessed**           | Yes                                                                                    |
| **Reproduced**         | No                                                                                     |
| **Fix pull requests**  | No                                                                                     |
| **Credits**            | Container pool. See [Assessment Credits](/konvu/administration/assessment-credits.md). |

## What Konvu checks

Container vulnerabilities have their own **OS exploitability checklist**, separate from the dependency checklist: the operating-system conditions that must hold for the vulnerability to be exploitable. The finding shows whether each condition holds, with a link to the evidence.

For Wiz findings, Konvu matches the image by the digest synced from your [AWS connection](/konvu/get-started/connect-your-environment/cloud/amazon-web-services.md), so the assessment runs against the exact image Wiz scanned.

Findings are grouped by repository and CVE. Switch between all image versions and the latest version per repository.

## Results

Container findings use the same results as dependencies: **Exploitable**, **False Positive**, **Needs input**, and **Inconclusive**. See [How Assessments Work](/konvu/triage-and-remediation/exploitability-assessment/how-assessments-work.md).

## Act on the results

* **Forward assessments to Wiz.** Turn on **Push results directly to Wiz** and Konvu adds an assessment note to the matching Wiz finding. Konvu writes notes only. It never changes status or severity in Wiz. See [Wiz](/konvu/get-started/bring-in-findings/container-and-cloud-scanners/wiz.md).
* **Fix exploitable findings** by rebuilding the image with the patched package version shown on the finding.

## What Konvu does NOT do

* It does not generate fix pull requests or rebuild images.
* It does not reproduce container findings.
* It does not write back to AWS Inspector or Snyk.
* It connects to Amazon ECR only. Other registries (GCR, Docker Hub, Harbor) are not supported yet.


---

# 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://docs.konvu.com/konvu/triage-and-remediation/finding-types/containers.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.