Container Registry

This section allows you to define the list of container registries that can be used within your organization. Only images stored on those container registries are allowed to be deployed on your cluster.

You can access this section by opening the Organization Settings -> Container Registries

When accessing the interface for the first time, you will see that a container registry already exist (called "registry-{$UIID}"). This container registry is created by Qovery on your infrastructure and is used to manage the deployment of your applications. You are free to use them to store your applications but you need to retrieve the credentials from your cloud provider console.

Create a Container Registry

By clicking on "Add Registry" you will be able to create a new Container Registry by filling these information:

• Registry Name
• Description
• Registry Url: the base url of the registry (example: https://docker.io, https://public.ecr.aws etc..)
• Registry type: you can chose among DockerHub, Public ECR, ECR (AWS private CR), Scaleway CR (Scaleway private CR), Github Packages, Gitlab CR, Generic.
• Credentials: these depends on the chosen registry type. If a container registry is public, you don't need to fill this part.

Important information:

• If you select Docker Hub, we encourage you to set credentials to increase the limits on the pull rate. See here for more details
• If the registry you need is not in the list and it supports the docker login format you can use the “Generic” registry.

Now that you have created the registry, you can start using it in order to create and deploy a service using the images stored within it.

Modify or Delete an existing registry

You can modify an existing container registry by clicking on the "Wheel" button next to it You can delete an existing container registry by clicking on the "Trash" button next to it

Before deleting it, make sure that there is no application within your organization using an image stored in this registry.