---
title: "Registries, images, and tags"
description: "How a TIR Container Registry, its images, their tags, and the artifacts behind the tags fit together, and what an image address looks like."
content_type: "concept"
product: "tir-container-registry"
platform: "TIR"
url: "/tir/tir-container-registry/concepts/registries-images-and-tags/"
---

# Registries, images, and tags

A registry holds images. Each image holds one or more artifacts, and each artifact carries one or
more tags.

| Term         | What it is                                                                                                                                |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Registry** | A namespace under which your images are organized. It belongs to one project and one region, and its name is part of every image address. |
| **Image**    | A versioned, layered container template built from a Dockerfile. An image can have several tags.                                          |
| **Artifact** | One version of an image's content. TIR shows it as **Artifacts Count** on the image.                                                      |
| **Tag**      | A name, such as `v1.0` or `latest`, for an artifact. Several tags can name the same artifact.                                             |

## Image addresses

An image address has the form `<endpoint>/<namespace>/<image>:<tag>`, for example
`registry.e2enetworks.net/my-namespace/my-app:v1.0`. The endpoint is `registry.e2enetworks.net` in Delhi
and `in-south1-registry.e2enetworks.net` in Chennai.

The pull command on the **Images** tab uses `@<digest>` in place of `:<tag>`, so it always pulls the
same content, even if the tag later points somewhere else.

## Tags that share content

When two tags name the same content, deleting one deletes both. See
[Delete a tag](/tir/tir-container-registry/how-to/delete-a-tag/).

## Access

In TIR, you need Read permission on Container Registry to view a registry, Create to make one, and
Delete to remove one. Docker signs in with the registry's own username and password instead. See
[Log in to a registry](/tir/tir-container-registry/how-to/log-in-to-a-registry/).