Docker Hub public and private repos - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Docker Hub Repository Visibility

Which statement correctly describes the difference between a public and a private repository on Docker Hub?

A Public repositories are free and accessible by anyone, while private repositories require a paid plan and restrict access to authorized users only.

B Private repositories are free and accessible by anyone, while public repositories require a paid plan and restrict access to authorized users only.

C Both public and private repositories require paid plans but differ in storage limits.

D Public repositories require authentication to pull images, private repositories do not.

💡 Hint

Think about who can access the images without logging in.

Public repositories are open to everyone and free to use. Private repositories restrict access and usually require a paid subscription.

💻 Command Output

intermediate

Docker Pull from Private Repository Without Login

What will be the output when running docker pull myusername/myprivaterepo:latest without logging in to Docker Hub?

Docker

docker pull myusername/myprivaterepo:latest

A Docker daemon crashes with segmentation fault

B Image pulled successfully without any authentication

C Warning: Image is deprecated but pulled successfully

D Error response from daemon: pull access denied for myusername/myprivaterepo, repository does not exist or may require 'docker login'

💡 Hint

Consider what happens when you try to access a private repo without credentials.

Docker requires authentication to pull images from private repositories. Without login, it denies access.

🔀 Workflow

advanced

Steps to Push an Image to a Private Docker Hub Repository

Arrange the following steps in the correct order to push a Docker image to a private repository on Docker Hub.

A 4,1,2,3

B 2,4,1,3

C 4,2,1,3

D 1,4,2,3

💡 Hint

Think about building first, then logging in, tagging, and finally pushing.

You first build the image locally, then login to Docker Hub, tag the image with your repo name, and push it.

❓ Troubleshoot

advanced

Diagnosing Docker Pull Failure from Private Repo

You run docker pull myusername/myprivaterepo:latest and get the error: unauthorized: authentication required. What is the most likely cause?

A You forgot to run <code>docker login</code> before pulling the image.

B The image tag 'latest' does not exist in the repository.

C Docker daemon is not running on your machine.

D Your internet connection is down.

💡 Hint

Think about authentication requirements for private repos.

Private repositories require authentication. Without logging in, Docker cannot pull the image.

✅ Best Practice

expert

Securing Access to Private Docker Hub Repositories

Which practice is the best way to securely manage access to private Docker Hub repositories in a team environment?

A Share the Docker Hub account password with all team members to allow direct login.

B Use Docker Hub organization accounts with team roles and individual user access control.

C Push images only from a single machine to avoid multiple credentials.

D Make the repository public temporarily when team members need access.

💡 Hint

Think about managing access without sharing passwords.

Using organization accounts with role-based access control allows secure and manageable access for teams.