Docker Hub public and private repos - Commands & Configuration

Introduction

Docker Hub is a place where you can store and share your container images. Public repos are free and visible to everyone, while private repos keep your images secret and only accessible to you or your team.

When you want to share your app image with the world for others to use or learn from.

When you need to keep your app image private for security or business reasons.

When you want to organize your images in a central place accessible from any computer.

When you want to automate deployment by pulling images directly from Docker Hub.

When you want to control who can see or download your images.

Commands

This command logs you into Docker Hub so you can push or pull images from your account.

Terminal

docker login

Expected Output

Login with your Docker ID to push and pull images from Docker Hub

Username: exampleuser

Password: 

Login Succeeded

Tags your local image 'my-app' with your Docker Hub username and repo name so it can be pushed.

Terminal

docker tag my-app exampleuser/my-app:latest

Expected Output

No output (command runs silently)

Uploads your tagged image to your Docker Hub repository, making it available online.

Terminal

docker push exampleuser/my-app:latest

Expected Output

The push refers to repository [docker.io/exampleuser/my-app]

latest: digest: sha256:abcdef1234567890 size: 1234

Downloads the image from Docker Hub to any machine, so you can run it there.

Terminal

docker pull exampleuser/my-app:latest

Expected Output

latest: Pulling from exampleuser/my-app

Digest: sha256:abcdef1234567890

Status: Downloaded newer image for exampleuser/my-app:latest

Logs you out of Docker Hub to keep your credentials safe when you finish working.

Terminal

docker logout

Expected Output

Removing login credentials for https://index.docker.io/v1/

Key Concept

If you remember nothing else, remember: public repos share images openly, private repos keep images secure and restricted.

Common Mistakes

Trying to push an image without logging in first

Docker Hub requires authentication to push images, so the push will fail.

Always run 'docker login' and enter your credentials before pushing images.

Not tagging the image with your Docker Hub username before pushing

Docker won't know which repository to push to, causing an error.

Use 'docker tag' to add your username and repo name to the image before pushing.

Trying to pull a private image without logging in

Private images require authentication, so pulling without login will be denied.

Run 'docker login' with your credentials before pulling private images.

Summary

Log in to Docker Hub to authenticate your actions.

Tag your local images with your Docker Hub username and repo name before pushing.

Push images to Docker Hub to share or store them.

Pull images from Docker Hub to use them on any machine.

Log out when done to protect your credentials.

Practice

1. What is the main difference between a public and a private Docker Hub repository?

easy

A. Public repos are open to everyone; private repos restrict access to authorized users only.

B. Public repos require payment; private repos are always free.

C. Public repos can only store images; private repos can store containers.

D. Public repos require docker login; private repos do not.

Solution

1. Step 1: Understand repository access types

   Public repositories are accessible by anyone without restrictions, while private repositories limit access to specific users.

2. Step 2: Identify the key difference

   The key difference is about who can access the repository: public is open, private is restricted.

3. Final Answer:

   Public repos are open to everyone; private repos restrict access to authorized users only. -> Option A

4. Quick Check:

   Access control = Public open, Private restricted [OK]

Hint: Public means open access; private means restricted access [OK]

Common Mistakes:

• Confusing payment requirements for public/private repos
• Thinking private repos store containers instead of images
• Believing public repos require login

2. Which command is used to authenticate your Docker client to access private Docker Hub repositories?

easy

A. docker pull

B. docker login

C. docker push

D. docker build

Solution

1. Step 1: Identify authentication command

   The command docker login is used to provide credentials to Docker Hub for private repo access.

2. Step 2: Differentiate from other commands

   docker pull downloads images, docker push uploads images, and docker build creates images locally.

3. Final Answer:

   docker login -> Option B

4. Quick Check:

   Authentication command = docker login [OK]

Hint: Use docker login to authenticate before accessing private repos [OK]

Common Mistakes:

• Using docker pull to authenticate
• Confusing push with login
• Trying to build to authenticate

3. What will happen if you try to pull an image from a private Docker Hub repository without logging in first?

medium

A. Docker will automatically log you in using your local credentials.

B. The image will download successfully without any error.

C. Docker will prompt for login credentials or show an authentication error.

D. The image will be pulled but with limited functionality.

Solution

1. Step 1: Understand private repo access control

   Private repositories require authentication before allowing image downloads.

2. Step 2: Predict Docker behavior without login

   If you are not logged in, Docker will deny access and prompt for credentials or show an error.

3. Final Answer:

   Docker will prompt for login credentials or show an authentication error. -> Option C

4. Quick Check:

   Unauthenticated pull from private repo = error prompt [OK]

Hint: Without login, pulling private images triggers authentication error [OK]

Common Mistakes:

• Assuming image downloads without login
• Thinking Docker auto-logs in
• Believing partial image pull is possible

4. You ran docker login but still get 'unauthorized' errors when pulling from a private repo. What is the most likely cause?

medium

A. You logged in with the wrong Docker Hub username or password.

B. The image name is misspelled but login was successful.

C. Docker Hub is down and cannot authenticate users.

D. You need to run docker logout before pulling.

Solution

1. Step 1: Check login credentials

   Unauthorized errors after login usually mean the credentials were incorrect or lack permission.

2. Step 2: Rule out other causes

   Misspelling causes 'not found' errors, not unauthorized. Docker Hub downtime is rare and would affect all users. Logout is not required before pulling.

3. Final Answer:

   You logged in with the wrong Docker Hub username or password. -> Option A

4. Quick Check:

   Unauthorized error after login = wrong credentials [OK]

Hint: Unauthorized after login? Check username/password carefully [OK]

Common Mistakes:

• Assuming image name typo causes unauthorized error
• Thinking logout fixes unauthorized errors
• Blaming Docker Hub downtime without checking credentials

5. You want to push a Docker image to a private repository on Docker Hub named myuser/myapp. Which sequence of commands correctly prepares and uploads the image?

hard

A. docker build myapp && docker push myuser/myapp && docker login

B. docker pull myuser/myapp && docker login && docker push myapp

C. docker push myapp && docker login && docker tag myapp myuser/myapp

D. docker login && docker tag myapp myuser/myapp && docker push myuser/myapp

Solution

1. Step 1: Authenticate with Docker Hub

   Run docker login to authenticate before pushing to a private repo.

2. Step 2: Tag the local image with the repository name

   Use docker tag myapp myuser/myapp to prepare the image for upload.

3. Step 3: Push the tagged image to the private repo

   Run docker push myuser/myapp to upload the image.

4. Final Answer:

   docker login && docker tag myapp myuser/myapp && docker push myuser/myapp -> Option D

5. Quick Check:

   Login, tag, then push = correct sequence [OK]

Hint: Login first, tag image with repo, then push [OK]

Common Mistakes:

• Pushing before login
• Pushing without tagging image correctly
• Pulling instead of tagging before push