> For the complete documentation index, see [llms.txt](https://docs.valohai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.valohai.com/docker-in-valohai/private-docker-registries/gcp.md).

# GCP Artifact Registry

Configure Valohai to pull private images from Google Cloud Artifact Registry.

> Private registries are restricted to organization projects. Personal projects don't have access to private repositories.

## Create a service account

1. Navigate to your Google Cloud project that hosts the Artifact Registry
2. Go to **IAM & Admin** → **Service Accounts**
3. Click **Create Service Account**
4. Add roles:
   * **Service Account Token Creator** (allows self-token creation)
   * **Artifact Registry Reader** (allows pulling images)
5. Create and download the **JSON key file**

Read more: [GCP Artifact Registry access control](https://cloud.google.com/artifact-registry/docs/access-control#permissions)

## Add credentials to Valohai

1. Navigate to `Hi, <n>` (top-right menu) → `Manage <organization>`
2. Go to **Registries** under organization controls
3. Click **Add a new entry**
4. Configure:
   * **Match pattern**: `<region>-docker.pkg.dev/<project-id>/*`
     * Example: `us-central1-docker.pkg.dev/my-project/*`
     * Or narrow it: `us-central1-docker.pkg.dev/my-project/ml-images/*`
   * **Registry type**: GCP Artifact Registry
   * **Service Account JSON**: Paste the entire contents of your JSON key file
5. Save

## Use the private image

Reference your Artifact Registry image in `valohai.yaml`:

```yaml
- step:
    name: train
    image: us-central1-docker.pkg.dev/my-project/ml-images/training:v1.0
    command:
      - python train.py
```

Valohai handles authentication automatically.


---

# 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.valohai.com/docker-in-valohai/private-docker-registries/gcp.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.