Menu

1 / 2

30-Day Cloud & DevOps Challenge: Day 11 — Pushing Docker Images to Registry

DEV Community·Michelle·7 months ago
#r5836W01
#why#understanding#docker#push#pipeline
Reading 0:00
15s threshold

Yesterday, my Jenkins pipeline could build Docker images for backend and frontend.

But those images only existed on my local machine. They weren't accessible anywhere else, not on another developer's computer, not on a cloud server, not anywhere.

Today, I fixed that. I configured Jenkins to push Docker images to Docker Hub a public registry where anyone can pull my images.

Now my images are available everywhere.

First: What is a Docker Registry?

The Analogy

Concept Analogy

Docker image A shipping container with your app

Docker registry A shipping port where containers are stored

Docker Hub The largest public shipping port

docker pull Bringing a container FROM the port

docker push Sending a container TO the port

Why Push to a Registry?

Without Registry With Registry

Images only on your laptop Images available anywhere

Can't share with team Anyone can pull the image

Need to rebuild on every server Pull once, run anywhere

No versioning Tag versions (v1.0, latest)

Step 1: Create Docker Hub…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.