# Understanding the Repositories Tab in Ace Container Registry

Once you've created a registry in AceCloud, the **Repositories** tab becomes the central place to manage and view all your container repositories. This article explains the functionality of this tab, including how to push Docker and Helm charts to your registry.

{% stepper %}
{% step %}

### Navigating to the Repositories Tab

* Log in to the AceCloud Console.
* Select your **Project** and **Region**.
* Go to **Container Registry**, click **Overview**.
* By default, the **Repositories** tab is selected.
  {% endstep %}

{% step %}

### What You’ll See in the Repositories Tab

* A list of all repositories (for example: nginx, app-backend, helm-charts)
* For each repository:
  * **Tags** (versions) of the container images
  * **Last Updated Time**
  * **Size**
  * **Vulnerability Scan Status** (if enabled)
    {% endstep %}

{% step %}

### Push Instructions (Docker & Helm)

At the top of the **Repositories** tab, you’ll find push instructions for both Docker and Helm.
{% endstep %}
{% endstepper %}

<figure><img src="/files/vRYzqQ7QC9cAYXCNP9Yh" alt=""><figcaption></figcaption></figure>

## Docker Push Command

Tag an image for this project:

```bash
docker tag SOURCE_IMAGE[:TAG] ace-registry-noi.acecloud.ai/test_registry/REPOSITORY[:TAG]
```

Push an image to this project:

```bash
docker push ace-registry-noi.acecloud.ai/test_registry/REPOSITORY[:TAG]
```

***

## Helm Push Command

Package a chart for this project:

```bash
helm package CHART_PATH
```

Push a chart to this project:

```bash
helm push CHART_PACKAGE oci://ace-registry-noi.acecloud.ai/test_registry
```


---

# 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.acecloud.ai/knowledge-base/registry/understanding-the-repositories-tab-in-ace-container-registry.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.