---
title: "Create a registry project"
description: "Create a private Container Registry project in MyAccount to hold your Docker images, with optional vulnerability prevention."
content_type: "how-to"
product: "container-registry"
platform: "MyAccount"
url: "/myaccount/container-registry/how-to/create-a-registry-project/"
topic: ["create-and-connect"]
---

# Create a registry project

Create a registry project to hold your Docker images. Every registry project is private. Its name
becomes part of every image path, such as `registry.e2enetworks.net/<project-name>/<repository>`, so
choose it with care: the name is fixed once the project is created.

## Before you begin

- MyAccount is set to Delhi, the region Container Registry is available in.
- The MyAccount project you want the registry project in is selected. A registry project belongs to
  the MyAccount project that was selected when it was created, and **Container Registry** lists only
  the registry projects of the selected MyAccount project. Each MyAccount project holds up to 20
  registry projects that have finished creating.
- If you are a team member, your role has the create permission for Container Registry.

## Open the create form

In MyAccount, under **Storage**, click **Container Registry**.

- With no registry project yet, the page opens on a form headed
  **Create your Private Container Registry**.
- Once you have a project, the page is headed **Manage Container Registry**. Click **+**
  (**Create Container Registry**). The **Add Container Registry** dialog opens, with the same
  fields.

## Name the project

**Project Name** starts with a random name such as `cr-12345`. Keep it, or replace it with your own.
A name:

- is 2 to 50 characters long
- starts with a lowercase letter
- uses lowercase letters and numbers, with single dots, underscores, or hyphens only between other
  characters

Choose a name that no registry project uses yet, in your account or in any other. The name is fixed
once the project is created.

## (Optional) Turn on vulnerability prevention

To keep images with known vulnerabilities from being pulled, check
**Prevent vulnerable images from running.** and choose a **Severity Level**: **Critical**, **High**,
**Medium**, **Low**, or **None**. Docker cannot pull any image with a vulnerability at the level you
choose or higher. The further down the list you choose, the more images are stopped: **Critical**
stops only images with critical vulnerabilities, and **None** stops every image with any
vulnerability. Every image is scanned when you push it. Start with **Critical** to stop only images
with critical vulnerabilities.

**Severity Level** starts at **None**, the strictest level, on the first-project form and at
**Critical** in the **Add Container Registry** dialog, so check it before you create the project.
With prevention off, the level has no effect, and every image pulls. You can turn prevention on or
off, and change the level, later on the project's **Configuration** tab; see
[Scan a project, repository, or artifact](/myaccount/container-registry/how-to/scan-a-project-repository-or-artifact/).

## Create it

The form shows the storage price. For current prices, see
[E2E's pricing page](https://www.e2enetworks.com/pricing).

Click **Create Project**. The form shows **Container Registry Setup In Progress**, and the project
reads **Creating** in the project list. The list refreshes itself every five seconds until the
project reads **Created**. When the project finishes creating, E2E emails the account's owner, with
you in copy.

Click the project in the list. Its tabs open: **Repositories**, **Configuration**,
**Source Registries**, **Replications Rules**, **Access token**, and **Image Cleanup**. The tabs
appear once the project reads **Created**.

If the name is refused, see
[Troubleshooting Container Registry](/myaccount/container-registry/troubleshooting/container-registry/#the-project-name-is-refused).
If the project reads **Failed**, see
[Troubleshooting Container Registry](/myaccount/container-registry/troubleshooting/container-registry/#the-project-reads-failed).

Your registry project is ready. Next, create an access token so Docker can log in to it; see
[Create an access token](/myaccount/container-registry/how-to/create-an-access-token/).