> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/continuous-vulnerability-elimination-factory-cvef/sbom360/generate-an-sbom/container-image-as-source/private-container-image.md).

# Private Container Image

SBOMs can be generated for private code repositories.

There are three steps involved:

### Step 1: Details

* Each configuration requires a mandatory name and a description.

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2FyjSkJwk18PnjCz8f0TnO%2Fimage.png?alt=media&amp;token=8b6b24f5-60ab-4ea8-a8f1-a861f6c2848c" alt=""><figcaption></figcaption></figure>

### Step 2: Configure

* Enter the credentials required to access the private registry. This gives Lineaje access to your organization’s private image registry,
* This step varies for AWS-ECR, GCP-Container Registry, and Docker Hub.
* By clicking on Test Connection, the connection will be tested against the credentials.

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2F2iZys0h5owMDzAC21W9u%2Fimage.png?alt=media&amp;token=2becdc1f-ae57-436f-9f2d-a90d27a63086" alt=""><figcaption></figcaption></figure>

### Step 3: Review

* All the container images available in the private registry will be displayed
* Choose a container image
* Project name and version will be auto generated but can be edited
* Click on Save Configuration to generate a project


---

# 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.veedna.com/continuous-vulnerability-elimination-factory-cvef/sbom360/generate-an-sbom/container-image-as-source/private-container-image.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.