> For the complete documentation index, see [llms.txt](https://docs.dyrector.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dyrector.io/tutorials/add-your-registry/add-v2-registry.md).

# Add V2 Registry

V2 Registries are Docker Registry HTTP API V2 compatible. Both private and public registries are supported.

### Add a private registry

**Step 1:** Open Registries on the left and click ‘Add’ on the top right.

**Step 2:** Enter your registry’s name and select an icon.

{% hint style="success" %}
**Tip:** You can write a description, so others on your team can understand what’s the purpose of this registry.
{% endhint %}

**Step 3:** Select V2 Registry and switch the toggle under the URL field to ‘Private’.

![](https://315393028-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCNvxW8k55ZlpJfMk8Oep%2Fuploads%2F6iSGxpzPO6owXBrPgr6k%2Fdyrector-io-v2-registry.png?alt=media\&token=0049a2ea-b106-4835-b6de-f4fa45ebfada)

**Step 4:** In the corresponding fields, enter:

* URL of your registry without the /v2 suffix,
* username, and
* the token or password which you use to access it.

**Step 5:** Click ‘Save’ button on the top right.

### **Add a public registry**

**Step 1:** Open Registries on the left and click ‘Add’ on the top right.

**Step 2:** Enter your registry’s name and select an Icon below.

{% hint style="success" %}
**Tip:** You can write a description, so others on your team can understand what’s the purpose of this registry.
{% endhint %}

**Step 3:** Select V2 Registry type and switch the toggle under the URL field to ‘Public’.

**Step 4:** Enter the URL of your registry without the /v2 suffix.

**Step 5:** Click ‘Save’ button on the top right.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dyrector.io/tutorials/add-your-registry/add-v2-registry.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.