> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/containers/private-container-registry/dcd-how-tos/create-container-registry.md).

# Create a Private Container Registry

Create a Private Container Registry via the DCD. After creating a Private Container Registry, you can store and manage Docker and OCI images privately, enable vulnerability scanning to detect CVEs in your artifacts, and choose the deployment location where your Private Container Registry and its artifacts will be hosted.

{% hint style="info" %}
**Prerequisites:** Ensure you have the appropriate permissions. Only contract administrators, owners, and users with the **Access and manage Private Container Registry** permission can create a Private Container Registry.
{% endhint %}

1\. In the **DCD**, go to **Menu** > **Containers** > **Container Registry**.

2\. Select **Add a Registry** in the **Container Registry** window to create a new Private Container Registry.

3\. Provide an appropriate **Name**.

{% hint style="warning" %}
**Important:**

* You cannot change the **Name** or the **Location** after the creation of a Private Container Registry.
* Ensure that the Private Container Registry **Name** is:
  * Globally unique across all customers.
  * Contains only alphanumeric characters and dashes.
  * Is between 3 and 63 characters long.
  * Begins with a character between a-z.
  * Ends with an alphanumeric character.
    {% endhint %}

4\. Choose the **Location** from the drop-down list where you want your Private Container Registry to run and your artifacts to be stored.

5\. Turn on the **Vulnerability Scanning** toggle.

{% hint style="warning" %}
**Important:** It is recommended that you create your Private Container Registry with **Vulnerability Scanning** enabled:

* It is a paid add-on and you will be charged for this service.
* You can turn it on for a Private Container Registry which does not have it enabled.
* You cannot disable it once it is enabled.
* Your container image artifacts will be scanned for CVEs when pushed to a Private Container Registry and every time CVE databases are updated with newly identified CVEs.
  {% endhint %}

6\. Click **Add Registry**.

![Enter the values for creating a Private Container Registry](/files/jqno3IkFIMFrVJEFGgRq)

{% hint style="success" %}
**Result:** Your Private Container Registry is ready to use when its status is updated to **Running**.
{% endhint %}

![The Private Container Registry is ready to use](/files/9pRQV9M90dflj9OMfno3)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ionos.com/cloud/containers/private-container-registry/dcd-how-tos/create-container-registry.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.