Why registries store and distribute images in Docker - Why It Works

Introduction

Docker registries keep copies of container images so you can share and reuse them easily. They solve the problem of moving images between computers and teams without rebuilding every time.

When you want to share your app image with teammates or other servers.

When you need to deploy the same container image on multiple machines.

When you want to save storage by reusing images instead of rebuilding.

When you want to keep a backup of your container images in a central place.

When you want to use public images from others without downloading them manually.

Commands

This command downloads the nginx image version 1.23.3 from Docker Hub, a public registry. It shows how registries distribute images to your local machine.

Terminal

docker pull nginx:1.23.3

Expected Output

1.23.3: Pulling from library/nginx

Digest: sha256:abc123def456...

Status: Downloaded newer image for nginx:1.23.3

docker.io/library/nginx:1.23.3

This command lists all images stored locally on your machine, including the one just pulled from the registry.

Terminal

docker images

Expected Output

REPOSITORY   TAG       IMAGE ID       CREATED       SIZE

nginx        1.23.3    123abc456def   2 weeks ago   133MB

This tags the nginx image with a new name to prepare it for uploading to your own registry or Docker Hub under your username.

Terminal

docker tag nginx:1.23.3 myusername/myapp:latest

Expected Output

No output (command runs silently)

This uploads your tagged image to the Docker Hub registry so others or your servers can download it later.

Terminal

docker push myusername/myapp:latest

Expected Output

The push refers to repository [docker.io/myusername/myapp]

123abc456def: Pushed 

latest: digest: sha256:789xyz123abc size: 1234

Key Concept

Registries store container images centrally so you can easily share, reuse, and deploy them anywhere without rebuilding.

Common Mistakes

Trying to push an image without tagging it with your registry username.

Docker requires images to be tagged with the registry path before pushing, or it will fail.

Always tag your image with your username or registry path before pushing, e.g., docker tag nginx:1.23.3 myusername/myapp.

Pulling an image without specifying the correct tag.

Docker pulls the 'latest' tag by default, which may not be the version you want.

Specify the exact tag like nginx:1.23.3 to get the correct image version.

Summary

Docker registries keep container images so you can share and reuse them easily.

You pull images from registries to run containers locally or on servers.

You push your own images to registries after tagging them with your username.

Practice

1. Why do Docker registries store container images?

easy

A. To share and reuse images across different computers

B. To run containers directly on the registry server

C. To convert images into executable programs

D. To delete old images automatically

Solution

1. Step 1: Understand the purpose of registries

   Registries act as storage places for container images so they can be accessed by many users or systems.

2. Step 2: Identify the benefit of storing images

   Storing images allows sharing and reusing them easily, speeding up deployment on different machines.

3. Final Answer:

   To share and reuse images across different computers -> Option A

4. Quick Check:

   Registries store images to share and reuse [OK]

Hint: Registries = storage for sharing images [OK]

Common Mistakes:

• Thinking registries run containers
• Believing registries convert images to programs
• Assuming registries delete images automatically

2. Which Docker command uploads an image to a registry?

easy

A. docker push

B. docker build

C. docker run

D. docker pull

Solution

1. Step 1: Recall Docker commands related to registries

   "docker push" uploads images to a registry, while "docker pull" downloads them.

2. Step 2: Match the command to the upload action

   Since uploading means sending images to the registry, "docker push" is correct.

3. Final Answer:

   docker push -> Option A

4. Quick Check:

   Upload image = docker push [OK]

Hint: Push means upload to registry, pull means download [OK]

Common Mistakes:

• Confusing push with pull
• Using docker run to upload images
• Thinking docker build uploads images

3. What happens when you run docker pull nginx?

medium

A. It uploads the nginx image to your local registry

B. It deletes the nginx image from your system

C. It builds a new nginx image from source code

D. It downloads the nginx image from a registry to your computer

Solution

1. Step 1: Understand the docker pull command

   "docker pull" downloads an image from a remote registry to your local machine.

2. Step 2: Identify the effect of pulling nginx

   Running "docker pull nginx" fetches the official nginx image from the registry to your computer.

3. Final Answer:

   It downloads the nginx image from a registry to your computer -> Option D

4. Quick Check:

   docker pull downloads images [OK]

Hint: Pull = download image from registry [OK]

Common Mistakes:

• Thinking pull uploads images
• Confusing pull with build
• Assuming pull deletes images

4. You run docker push myapp but get an error saying 'repository not found'. What is the likely cause?

medium

A. Docker daemon is not running

B. The image name is misspelled locally

C. You forgot to log in to the registry before pushing

D. You used docker pull instead of docker push

Solution

1. Step 1: Analyze the error message

   'repository not found' usually means the registry does not recognize your image because you lack permission or authentication.

2. Step 2: Identify missing login step

   Before pushing, you must log in to the registry with "docker login" to authenticate and allow image upload.

3. Final Answer:

   You forgot to log in to the registry before pushing -> Option C

4. Quick Check:

   Push error 'repository not found' = missing login [OK]

Hint: Login before push to avoid repository errors [OK]

Common Mistakes:

• Assuming image name typo causes this error
• Ignoring Docker daemon status
• Confusing push with pull commands

5. You want to deploy the same app on multiple servers quickly. How does using a Docker registry help?

hard

A. It runs the app on the registry server for all clients

B. It stores the app image centrally so all servers can download it fast

C. It converts the app into a virtual machine image

D. It automatically updates the app code on all servers

Solution

1. Step 1: Understand the role of registries in deployment

   Registries hold container images centrally, making them accessible to many servers without rebuilding.

2. Step 2: Connect central storage to fast deployment

   Servers pull the image from the registry quickly, enabling fast and consistent app deployment everywhere.

3. Final Answer:

   It stores the app image centrally so all servers can download it fast -> Option B

4. Quick Check:

   Registry centralizes images for fast multi-server deployment [OK]

Hint: Central image storage speeds multi-server deployment [OK]

Common Mistakes:

• Thinking registry runs apps for clients
• Confusing container images with virtual machines
• Assuming registry auto-updates app code