Pulling images from Docker Hub - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Output of Docker pull command with tag

What is the output when you run docker pull nginx:alpine on a system that does not have the image locally?

Docker

docker pull nginx:alpine

A

Using default tag: latest
latest: Pulling from library/nginx
Digest: sha256:...
Status: Downloaded newer image for nginx:alpine

B Error response from daemon: manifest for nginx:alpine not found

C

alpine: Pulling from library/nginx
Digest: sha256:...
Status: Downloaded newer image for nginx:alpine

D

Using default tag: alpine
alpine: Pulling from library/nginx
Digest: sha256:...
Status: Downloaded newer image for nginx:alpine

💡 Hint

The command specifies the tag explicitly; Docker does not use 'latest' as default in this case.

When you specify a tag like 'alpine', Docker pulls that specific tag. The output shows the tag being pulled and the status of the download. Option C is wrong because it says 'latest' tag is used by default, which is not true when a tag is specified. Option C is wrong because 'Using default tag' message is not shown when tag is specified. Option C is wrong because the image exists.

🧠 Conceptual

intermediate

Understanding Docker image tags

Which statement correctly describes Docker image tags when pulling from Docker Hub?

A Tags are used only for local images and have no effect when pulling from Docker Hub.

B If no tag is specified, Docker pulls the 'latest' tag by default.

C Docker always pulls all tags of an image when pulling without a tag.

D Docker pull command requires a tag; otherwise, it fails.

💡 Hint

Think about what happens if you run 'docker pull ubuntu' without specifying a tag.

Docker uses the 'latest' tag by default if no tag is specified. It does not pull all tags, and tags are important for identifying image versions on Docker Hub. The pull command works without specifying a tag.

❓ Troubleshoot

advanced

Diagnosing Docker pull failure

You run docker pull myuser/myapp:1.0 and get the error: Error response from daemon: manifest for myuser/myapp:1.0 not found. What is the most likely cause?

A The tag '1.0' does not exist for the image 'myuser/myapp' on Docker Hub.

B The image 'myuser/myapp' does not exist on Docker Hub.

C Docker daemon is not running on your system.

D You are not logged in to Docker Hub.

💡 Hint

The error mentions 'manifest not found' for a specific tag.

The error 'manifest for myuser/myapp:1.0 not found' indicates the specific tag '1.0' does not exist for 'myuser/myapp' on Docker Hub (a non-existent repository produces a similar error). Docker daemon not running or login issues produce different errors.

🔀 Workflow

advanced

Sequence of commands to pull and run a Docker image

What is the correct order of commands to pull the official Redis image and run it as a container named 'myredis'?

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

You must pull the image before running a container from it.

First, pull the image to ensure it is available locally. Then run the container. Use 'docker ps' to check running containers. Finally, stop the container when done.

✅ Best Practice

expert

Optimizing Docker image pulls in CI pipelines

In a CI pipeline, you want to speed up builds by avoiding unnecessary Docker image pulls. Which approach is best?

A Use 'docker pull' with the specific image tag only if the image is not present locally.

B Skip pulling images and rely on the build process to download layers automatically.

C Always run 'docker pull' before building to ensure the latest image.

D Use a local Docker registry mirror and configure the daemon to pull from it.

💡 Hint

Think about reducing network latency and bandwidth usage in CI environments.

Using a local registry mirror caches images and speeds up pulls. Always pulling wastes time and bandwidth. Checking locally before pulling is manual and error-prone. Skipping pulls can cause inconsistent builds.