Google Cloud Container Registry

How to store container images in GCP

This is an older version of the ZenML documentation. To read and view the latest version please visit this up-to-date URL.

The GCP container registry is a container registry flavor which comes built-in with ZenML and uses the Google Artifact Registry or the Google Container Registry to store container images.

When to use it

You should use the GCP container registry if:

  • one or more components of your stack need to pull or push container images.

  • you have access to GCP. If you're not using GCP, take a look at the other container registry flavors.

How to deploy it

When using the Google Container Registry, all you need to do is enabling it here.

How to find the registry URI

When using the Google Container Registry, the GCP container registry URI should have one of the following formats:<PROJECT_ID>

# Examples:

To figure our the URI for your registry:

  • Go to the GCP console.

  • Click on the dropdown menu in the top left to get a list of available projects with their names and IDs.

  • Use the ID of the project you want to use fill the template<PROJECT_ID> and get your URI (You can also use the other prefixes <us/eu/asia> as explained above if you want your images stored in a different region).

How to use it

To use the Azure container registry, we need:

  • Docker installed and running.

  • The GCP CLI installed and authenticated.

  • The registry URI. Check out the previous section on the URI format and how to get the URI for your registry.

We can then register the container registry and use it in our active stack:

zenml container-registry register <NAME> \
    --flavor=gcp \

# Add the container registry to the active stack
zenml stack update -c <NAME>

Additionally, we'll need to configure Docker, so it can pull and push images:

gcloud auth configure-docker

For more information and a full list of configurable attributes of the GCP container registry, check out the API Docs.

Last updated