Skip to content
BENIBIX Learn

Container Registry

Infrastructure📦 ContainersImages and Registries

Also known as Image Registry, Docker Registry, Container Image Registry

A server that stores container images. You push them up and pull them down.

Think of it like

It is like a library for images. You put one on the shelf, and others can borrow it.

Example

Lucy's build pipeline pushes each new image to her team's private registry. The live servers pull version 2.3 from there and start it.

Why it matters

Servers need one trusted place to fetch images from. The registry is that place.

Definition

A container registry is a server that stores container images. You push an image up after you build it. Servers pull it down when they need to run it. Images are kept in named folders called repositories, with a tag for each version. A registry can be public for anyone, or private for one team.

Example code

bash
docker tag shop-app:2.3 registry.example.com/team/shop-app:2.3
docker push registry.example.com/team/shop-app:2.3
The new name says which registry and folder the image goes to. Push sends it there.
The registry sits between the build and the servers. Images go up once and come down many times.

Common mistake

Always pulling the latest tag. It can point to a new build at any time, so pin the version you tested.

Key takeaways

  1. 1
    Push and pull. Builds go up, servers fetch them down.
  2. 2
    Folders and tags. One folder holds all the versions of one image.
  3. 3
    Public or private. Open to all, or to one team.