# Overview

The <code class="expression">space.vars.ionos\_cloud</code> Container Registry is a universal repository manager with a recommended service for storing and managing custom container images and other artifacts in <code class="expression">space.vars.ionos\_cloud</code>. Deploying and pulling images can be done using the Docker CLI or added directly to a Kubernetes deployment.

![IONOS CLOUD Container Registry Architecture](/files/5ntQD54JBms9Yzuh3AdQ)

The <code class="expression">space.vars.ionos\_cloud</code> Container Registry provides users with a dedicated registry or multiple registries based on their contracts, allowing them to host their own Docker images without the need for an external provider (such as Docker Hub).

A container registry is created to store and share custom images in the same regions where you deploy them. Container Registry is a high-performance platform for storing custom image containers. It can be used as part of CI/CD workflows for container workloads.

You can order and manage the Container Registry through the API. The API will allow integration into the Data Center Designer (DCD).

## Specifications

The <code class="expression">space.vars.ionos\_cloud</code> Container Registry specifications are as follows:

|          Specification          |                                                              Status                                                             |
| :-----------------------------: | :-----------------------------------------------------------------------------------------------------------------------------: |
|         Docker Registry         |                                                               Yes                                                               |
|          Built-in CI/CD         | The container registry supports the Docker Registry HTTP v2 API, allowing it to be integrated into an automated CI/CD pipeline. |
| Built-in OSS Vulnerability Scan |                                                                No                                                               |

## Container Registry Characteristics

Our platform is responsible for providing the operations required to facilitate the distribution of images.

* The container registry is accessible from the public internet and maximally available (High availability setup) for pushing and pulling artifacts.
* The service is managed, including any components on which it is built.
* The container registry supports the [<mark style="color:blue;">Docker Registry HTTP API v2</mark>](https://docs.docker.com/registry/spec/api/), which allows it to be integrated into an automated CI/CD pipeline.
* It also supports authentication tokens for use by robot accounts to be able to integrate into an automated CI/CD pipeline. You can create a one-time token to allow the CI/CD pipeline to push a new image.
* You can use the registry with [<mark style="color:blue;">Docker Registry HTTP API v2</mark>](https://docs.docker.com/registry/spec/api/) compliant tools, e.g. [<mark style="color:blue;">Docker CLI</mark>](https://docs.docker.com/engine/reference/commandline/cli/).
* It is possible to use the same credentials to access all registries and repositories in the same <code class="expression">space.vars.ionos\_cloud</code> account that the user has access to.
* All data in the registry will be encrypted at rest.

## Regional availability

The <code class="expression">space.vars.ionos\_cloud</code> Container Registry is available in the **FRA** region.

## Pricing

For more information, see [<mark style="color:blue;">Private Container Registry</mark>](https://docs.ionos.com/cloud/support/general-information/price-list/ionos-cloud-eur-en#private-container-registry).

{% hint style="info" %}
**Note:** The network traffic is **not charged**.
{% endhint %}

## Rate Limit

Rate limits apply to your interactions with the Container Registry to ensure service stability, prevent resource monopolization, and protect the underlying infrastructure. Example: Deploying or pushing images. They specifically control the rate and volume of API calls and data transfers from any single client application or machine.

| **Metric**                                   | **Limit** | **Description**                                                                                                                                                                                                                                   |
| -------------------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Maximum Concurrent Connections per Client    | 100       | The highest number of simultaneous TCP connections that a single client (Example: a build server or cluster node) can maintain for registry operations, such as downloading layers. Exceeding this limit will result in the connection rejection. |
| Maximum Requests per Second (RPS) per Client | 60        | The maximum number of API requests (Example: fetches, token authentication requests, layer existence checks) that a single client can send to the registry per second. Excessive requests result in a 429 (Too Many Requests) error.              |


---

# Agent Instructions: 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:

```
GET https://docs.ionos.com/cloud/containers/private-container-registry/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.