Skip to content

ezgh registry

Container Registry: repositories, images, docker login and pull-through cache rules.

Updated View as Markdown
ezgh registry <command>

EZGH Container Registry keeps a project’s container images on its own registry host, <id>.registry.ezghcloud.com (ezgh registry get shows it). Push and pull them with docker or any OCI client at <host>/<scope>/<image>, signing in with an API key (ezgh registry login):

ezgh registry login
docker tag api:latest <host>/team-a/api:v1
docker push <host>/team-a/api:v1

Everything is in a project (--project, EZGH_PROJECT or the profile’s). A repository is given by ID (rep_…) or name (team-a/api); an image by digest.

A pull-through cache rule maps a prefix on that host to Docker Hub: the first pull of <host>/<prefix>/<namespace>/<repository> fetches the image with the rule’s Docker Hub credentials and stores it in the project, and later pulls are served from that copy.

Flags

This command also takes the global flags.

Subcommands

Command Description
ezgh registry cache-rules Pull-through cache rules: Docker Hub images through your registry
ezgh registry get Show the project’s registry host
ezgh registry get-login-password Print the API key to sign a container client in with
ezgh registry images Images in a repository, by digest
ezgh registry login Sign docker in to the project’s registry
ezgh registry repositories Repositories: where a project’s images are pushed and pulled
ezgh registry tags Tags in a repository
Navigation

Type to search…

↑↓ navigate↵ selectEsc close