---
title: "Container Registry"
description: "Private and public container images on each project's own registry host, and Docker Hub images pulled through it."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.ezghcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Container Registry

EZGH Container Registry keeps a project's container images on the project's own registry host,
`<id>.registry.ezghcloud.com`. Push and pull with docker, containerd or any OCI client, signing in
with an EZGH API key as the password (the username isn't checked):

```sh
echo "$EZGH_API_KEY" | docker login <id>.registry.ezghcloud.com -u ezgh --password-stdin
```

With the CLI, `ezgh registry get` shows the project's host, and `ezgh registry login` signs docker in
for you (`ezgh registry get-login-password` prints the password for podman, crane and other clients):

```sh
ezgh registry get
ezgh registry login
docker push <id>.registry.ezghcloud.com/team-a/api:v1
```

`ezgh registry repositories`, `images` and `tags` list and manage what the project holds; see the
[CLI reference](/cli/reference/registry). [EZGH Kubernetes](/kubernetes) nodes pull your organization's
private images with no image pull secret: use `<id>.registry.ezghcloud.com/<repository>:<tag>` as
the image.

In the console, open **Container Registry**: **Repositories** shows the project's host, its
repositories and their images, and **Pull-through cache** its cache rules.

- [Pull-through cache](/registry/pull-through-cache) — Pull Docker Hub images through your project's registry, with your own Docker Hub credentials.

Source: https://docs.ezghcloud.com/registry/index.mdx
