> ## Documentation Index
> Fetch the complete documentation index at: https://docs.krait.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Container Scanning

> Analyze your container images to identify known security vulnerabilities and reduce risk before deployment.

<Steps>
  <Step title="Connect DockerHub">
    Connect your DockerHub account to start scanning your container images.

    <Card title="DockerHub" icon="docker" href="/integrations/container#dockerhub">
      Connect your DockerHub registry
    </Card>
  </Step>

  <Step title="Sync images">
    After connecting DockerHub, sync the container images you want to scan. The number of images you connect will depend on the type of your workspace.

    <Frame>
      <img src="https://mintcdn.com/krait/9ioPUQVgYHbGs9dJ/scanning/images/sync_container.png?fit=max&auto=format&n=9ioPUQVgYHbGs9dJ&q=85&s=f179d34484737db8f797b452d171b228" alt="Sync container repositories interface" width="1382" height="740" data-path="scanning/images/sync_container.png" />
    </Frame>
  </Step>

  <Step title="Start scanning">
    Initiate a scan on your selected container images. The scan take a few minutes depending on the size and number of images.
  </Step>

  <Step title="View findings">
    Once the scan completes, findings will appear on the page.

    <Frame>
      <img src="https://mintcdn.com/krait/9ioPUQVgYHbGs9dJ/scanning/images/findings_container.png?fit=max&auto=format&n=9ioPUQVgYHbGs9dJ&q=85&s=f8cdc46d4e19249036af2151ea412c8b" alt="Container security findings dashboard" width="2002" height="1468" data-path="scanning/images/findings_container.png" />
    </Frame>
  </Step>

  <Step title="Analyze Findings">
    By clicking on any finding, you will see its detail. You will find a short explanation, the code snippet, catagory, severity, CVSS score, references. If a issue is present multiple times, Krait will only show one finding and group all the instances together. You can also create a ticket from the findings page.

    <Frame>
      <img src="https://mintcdn.com/krait/9ioPUQVgYHbGs9dJ/scanning/images/container-findings.png?fit=max&auto=format&n=9ioPUQVgYHbGs9dJ&q=85&s=50797431c53c32bee7582842cd1b5e88" alt="Security findings dashboard" width="1660" height="1364" data-path="scanning/images/container-findings.png" />
    </Frame>
  </Step>
</Steps>

Container scanning in Krait provides continuous visibility into security risks within your container images. By scanning images and reviewing actionable findings, teams can identify, prioritize, and remediate vulnerabilities before containers are deployed to production.

## Linking to Repositories

When a container and a code repository share the same application context, scanning them independently can produce duplicate findings for the same underlying issue. Linking a container to its corresponding repository lets Krait merge overlapping results, giving you a single clean list of findings with no repeated noise.

<Info>
  Each container can be linked to one repository only. You can unlink at any time without affecting your scans.
</Info>

<Steps>
  <Step title="Navigate to Containers">
    Go to **Assets**, then select **Containers**.
  </Step>

  <Step title="Open Link Repository">
    Click **Link Repository** to open the linking panel.

    <Frame>
      <img src="https://mintcdn.com/krait/9ioPUQVgYHbGs9dJ/scanning/images/linkrepo.png?fit=max&auto=format&n=9ioPUQVgYHbGs9dJ&q=85&s=3126d2688ee8aa6e2d9837bc9e7a3015" alt="Link repository interface" width="1834" height="866" data-path="scanning/images/linkrepo.png" />
    </Frame>
  </Step>

  <Step title="Select a Container and Repository">
    Choose a container from the list of connected containers, then select the repository you want to link it to from the list of connected repositories.
  </Step>

  <Step title="Confirm the Link">
    Click **Confirm**. Krait will now correlate findings across the linked container and repository, automatically deduplicating any overlapping vulnerabilities.
  </Step>
</Steps>

To unlink, return to **Assets**, select **Containers**, open the linked container, and click **Unlink Repository**.