> For the complete documentation index, see [llms.txt](https://docs.acecloud.ai/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.acecloud.ai/knowledge-base/registry/how-to-create-a-registry.md).

# How to create a registry?

This article explains how to create a container registry in AceCloud. Each project can have only one registry per region. Creating a registry is the first step in securely managing and distributing container images across your environments.

## **Steps to Create a Registry**

### **1. Navigate to Container Registry**

* Log in to the [AceCloud](https://customer.acecloudhosting.com/) Console.
* From the left-hand menu, go to **Registry** under your desired **Project** and **Region** and click **Overview**.

<figure><img src="https://4132105993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6xzVdxzgFAXWb0qJY9hx%2Fuploads%2FvKagc6JanbFQB7ff8n8K%2Fimage.png?alt=media&amp;token=274f110f-8f8d-4ace-af3a-dbabf4ddd6b4" alt=""><figcaption></figcaption></figure>

### **2. On the Container Registry page, click the Get Started button.**

<figure><img src="https://4132105993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6xzVdxzgFAXWb0qJY9hx%2Fuploads%2FZrddU02gPGOcB2kiLn7S%2Fimage.png?alt=media&amp;token=0117719c-8a52-49d1-80df-89736608fc72" alt=""><figcaption></figcaption></figure>

### **3. Enter Registry Name**

* In the *Create Registry* form, provide a unique **Registry Name**.

<figure><img src="https://4132105993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6xzVdxzgFAXWb0qJY9hx%2Fuploads%2F5tUkA737BzytR3MRjYW3%2Fimage.png?alt=media&amp;token=be03cc2a-db5d-453d-be14-2aecba31c30c" alt=""><figcaption></figcaption></figure>

📝 *Note: This name will also be used as the destination namespace for replication. Keep it consistent.*

### **4. Configure Immutable Rule (Optional)**

* Enable the **Immutable Rule** to prevent tags from being overwritten.

<figure><img src="https://4132105993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6xzVdxzgFAXWb0qJY9hx%2Fuploads%2FOmw2ekyLg5ICkZWkKUvb%2Fimage.png?alt=media&amp;token=ed9f4684-a3d8-438b-874f-277431958ffd" alt=""><figcaption></figcaption></figure>

Configure the following:

* **Repository Matching**: Specify repository names or patterns.
  * Use \* to match multiple repositories at the same level.
  * Use \*\* to match repositories across multiple levels.
* **Tag Matching / Excluding**: Define tag patterns (e.g., v1.\*, latest).
  * Use \* to match any sequence of characters in the tag.
  * Use \*\* for recursive matching across paths.

### **5. Enable Vulnerability Scanning (Optional)**

* Toggle the **Enable Vulnerability Scanning** checkbox.

<figure><img src="https://4132105993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6xzVdxzgFAXWb0qJY9hx%2Fuploads%2FnDn7g6HzJhgoXt5o9Rxl%2Fimage.png?alt=media&amp;token=c05539ce-6529-41c3-9a6d-ca44c526cb8b" alt=""><figcaption></figcaption></figure>

* This feature scans images for known security vulnerabilities when pushed.

### **6. Click on Create Registry**

* Review your settings and click **Create Registry**.

<figure><img src="https://4132105993-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6xzVdxzgFAXWb0qJY9hx%2Fuploads%2FyWzxvZmoYpX1gO9YttT7%2Fimage.png?alt=media&amp;token=2966546e-48c1-461f-9995-48af7c99cab8" alt=""><figcaption></figcaption></figure>

* The registry will be created and listed under the **Container Registry** section.

## **Important Notes**

* You can only have **one registry per project per region**.
* **Immutable tags** help avoid accidental overwrites.
* **Vulnerability scanning** improves image security by identifying threats early.
* **Destination namespace** (used during replication) should match the **registry name**
