E2E CloudContainer Registry
TIR Container Registry keeps your Docker container images private, in your TIR project. Push an image from your own machine with Docker, then run it on an instance, serve it from a model endpoint, or use it in a pipeline or a Kubernetes cluster. Each registry has its own username and password, the only credentials that can push or pull its images.
Where to find it
Section titled “Where to find it”In TIR, open your project. In the side menu, under Storage, select Container Registry. The page is Manage E2E Registries.
The three terms
Section titled “The three terms”| Term | What it is |
|---|---|
| Registry | A namespace under which your images are organized. Its name, the namespace, is part of every image address. |
| Image | A versioned, layered container template built from a Dockerfile. An image can have several tags. |
| Tag | A name for one version of an image, such as v1.0 or latest. Tags that point to the same content belong to one artifact. |
See Registries, images, and tags for how they fit together.
What you can do
Section titled “What you can do”Store images
Section titled “Store images”- Create a registry with a namespace and a username prefix.
- Log in to a registry with Docker.
- Push an image from your machine, and pull an image back.
- See the images in a registry, with their tags, sizes, and pull commands.
Use your images in TIR
Section titled “Use your images in TIR”- Create an instance from your own image.
- Deploy a custom container as a model endpoint.
- Run a Docker image as a pipeline.
- Pull images from Container Registry into a Kubernetes cluster.
Clean up
Section titled “Clean up”Where to start
Section titled “Where to start”Get started with TIR Container Registry takes you from creating a registry to pulling an image back. The TIR Container Registry FAQ has short answers, and Troubleshooting TIR Container Registry explains each message.