Overview
Connecting a private container registry lets the platform pull Docker images from it when running private tools. Once connected, images from that registry can be referenced in your private tool configurations without any extra authentication steps.Obtaining Credentials
Before connecting a registry, you will need a username and an access token or password. The exact steps depend on your provider: For any other registry that supports the Docker Registry HTTP API, use the username and password or token that grants read access to the relevant images.Adding a Registry
Navigate to Container Registry settings
Go to Settings > Infrastructure > Container Registry and click Add Registry.
Choose a registry type
Select one of the supported registry types. See the field reference below for what each type requires.
Docker Registry
Use this for any self-hosted registry or a registry that supports the Docker Registry HTTP API (including AWS ECR).| Field | Description |
|---|---|
| Name | Display name for this registry within the platform. |
| Registry URL | Full URL of the registry, including any namespace (e.g., aws_account_id.dkr.ecr.region.amazonaws.com/namespace). |
| Username | Registry username. |
| Password / Token | Registry password or access token. |
Docker Hub
| Field | Description |
|---|---|
| Name | Display name for this registry within the platform. |
| Docker Hub Username | Your Docker Hub username. |
| Access Token | A Docker Hub access token with read access to the relevant images. |
GitHub
| Field | Description |
|---|---|
| Name | Display name for this registry within the platform. |
| GitHub Username | Your GitHub username. |
| Personal Access Token | A GitHub personal access token with the read:packages scope. |