Registry mirroring concept in Docker - Step-by-Step Execution

Process Flow - Registry mirroring concept

Client requests image

↓

Check local registry cache

↓

Forward request to mirror registry

↓

Mirror registry fetches image

↓

Serve image to client

↓

Client pulls image

The client asks for an image. If the local cache has it, serve it. If not, forward the request to the mirror registry, which fetches and serves the image.

Execution Sample

Docker

docker pull myregistry.local/myimage:latest
# Local registry checks cache
# If missing, forwards to mirror
# Mirror fetches from upstream
# Image served back to client

This simulates pulling an image using a registry mirror that caches images locally.

Process Table

Step	Action	Local Registry Cache	Mirror Registry Action	Client Output
1	Client requests image 'myimage:latest'	Cache empty	Idle	Request sent
2	Local registry checks cache	Image not found	Idle	Waiting
3	Local registry forwards request to mirror	Cache empty	Receives request	Waiting
4	Mirror registry checks own cache	Cache empty	Image not found	Waiting
5	Mirror fetches image from upstream registry	Cache empty	Downloading image	Waiting
6	Mirror stores image in cache	Cache empty	Image cached	Waiting
7	Mirror serves image to local registry	Cache empty	Serving image	Waiting
8	Local registry caches image	Image cached	Idle	Receiving image
9	Local registry serves image to client	Image cached	Idle	Image received
10	Client completes pull	Image cached	Idle	Image ready locally

💡 Image successfully pulled and cached locally via mirror registry

Status Tracker

Variable	Start	After Step 3	After Step 6	After Step 8	Final
Local Registry Cache	empty	empty	empty	cached image	cached image
Mirror Registry Cache	empty	idle	cached image	cached image	cached image
Client State	request sent	waiting	waiting	receiving image	image ready

Key Moments - 3 Insights

Why does the local registry forward the request to the mirror?

Because the local registry cache is empty (see execution_table step 2), it cannot serve the image and must ask the mirror to fetch it.

When does the mirror registry cache the image?

After fetching the image from the upstream registry (step 6), the mirror stores it locally to serve future requests faster.

How does the client finally get the image?

The client receives the image after the local registry caches it and serves it back (step 9), completing the pull (step 10).

Visual Quiz - 3 Questions

Look at the execution table, at which step does the mirror registry start downloading the image?

A Step 6

B Step 4

C Step 5

D Step 7

💡 Hint

Check the 'Mirror Registry Action' column for when it changes to 'Downloading image'

According to the variable tracker, when does the local registry cache change from empty to cached image?

A After Step 8

B After Step 6

C After Step 3

D Final

💡 Hint

Look at 'Local Registry Cache' values across steps in variable_tracker

If the local registry already had the image cached, what would happen at Step 2?

A It would forward the request to the mirror

B It would serve the image directly to the client

C The mirror would fetch the image from upstream

D The client would wait indefinitely

💡 Hint

Refer to execution_table step 2 where cache is checked

Concept Snapshot

Registry mirroring caches images locally to speed up pulls.
Client requests image from local registry.
If missing, local forwards to mirror registry.
Mirror fetches from upstream and caches image.
Local registry caches image from mirror and serves client.
This reduces load and speeds up repeated pulls.

Full Transcript

Registry mirroring means a local registry stores copies of images from an upstream source. When a client asks for an image, the local registry first checks if it has it cached. If not, it asks the mirror registry to get it. The mirror fetches the image from the upstream registry, caches it, and sends it back to the local registry. Then the local registry caches it and serves the client. This process speeds up image pulls and reduces network load by reusing cached images locally.