Tagging images during build in Docker - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of tagging a Docker image during build?

Tagging a Docker image during build helps to give the image a meaningful name and version. This makes it easier to identify, manage, and deploy specific versions of the image.

beginner

How do you tag a Docker image during the build process?

You use the docker build command with the -t option followed by the tag name, like docker build -t myapp:1.0 . to tag the image as 'myapp' with version '1.0'.

intermediate

What does the tag latest mean in Docker images?

The latest tag is the default tag if none is specified. It usually points to the most recent or stable version of the image, but it is just a label and does not guarantee the newest image.

intermediate

Can you assign multiple tags to a Docker image during build?

Yes, you can assign multiple tags by using multiple -t options in the docker build command, for example: docker build -t myapp:1.0 -t myapp:stable .

beginner

Why is it important to use version tags instead of only latest?

Using version tags helps avoid confusion and errors by clearly specifying which image version to use. It improves deployment reliability and makes rollbacks easier if needed.

Which command tags a Docker image as 'myapp' with version '2.0' during build?

A docker build -t myapp:2.0 .

B docker tag myapp 2.0

C docker run -t myapp:2.0

D docker push myapp:2.0

The docker build -t myapp:2.0 . command builds the image and tags it as 'myapp' with version '2.0'.

What happens if you do not specify a tag when building a Docker image?

A The image is tagged as 'latest' by default

B The build fails

C The image is not saved

D Docker asks you to enter a tag

If no tag is specified, Docker automatically tags the image as 'latest'.

How can you assign two tags 'v1' and 'stable' to the same image during build?

A docker build -t myapp:v1,stable .

B docker build -t myapp:v1 -t myapp:stable .

C docker tag myapp:v1 stable

D docker build -tag myapp:v1 stable

You use multiple -t options to assign multiple tags during build.

Why should you avoid relying only on the 'latest' tag in production?

A Because 'latest' images cannot be pushed to registries

B Because 'latest' images are always unstable

C Because 'latest' tag is deprecated

D Because 'latest' may point to different images over time causing unpredictability

The 'latest' tag can change and may cause unexpected image versions to be deployed.

Which of these is NOT a valid Docker image tag format?

A myapp:beta-2

B myapp:1.0

C myapp:1.0-

D myapp:v1.0.0

Docker tags must not end with a hyphen or period; '1.0-' ends with a hyphen, making it invalid.

Explain how to tag a Docker image during the build process and why tagging is useful.

Think about how you name files to keep track of versions.

Describe the risks of using only the 'latest' tag for Docker images in production environments.

Consider what happens if you always use the newest file without knowing its exact version.

Practice

1. What is the purpose of using the -t option in the docker build command?

easy

A. To assign a name and tag to the image during build

B. To specify the Dockerfile location

C. To run the container after building the image

D. To remove intermediate containers after build

Solution

1. Step 1: Understand the docker build command options

   The -t option is used to tag the image with a name and optionally a tag.

2. Step 2: Identify the purpose of tagging

   Tagging helps to identify and manage images easily by giving them a readable name and version.

3. Final Answer:

   To assign a name and tag to the image during build -> Option A

4. Quick Check:

   -t tags image [OK]

Hint: Remember: -t means tag your image name during build [OK]

Common Mistakes:

• Confusing -t with specifying Dockerfile path
• Thinking -t runs the container
• Assuming -t deletes containers

2. Which of the following is the correct syntax to build a Docker image named myapp with tag v1 from the current directory?

easy

A. docker build -t myapp:v1 .

B. docker build myapp:v1 .

C. docker build -name myapp:v1 .

D. docker build --tag=myapp v1 .

Solution

1. Step 1: Recall the correct docker build syntax for tagging

   The correct syntax uses -t name:tag followed by the build context (here, .).

2. Step 2: Match the options with correct syntax

   docker build -t myapp:v1 . matches the correct syntax: docker build -t myapp:v1 .

3. Final Answer:

   docker build -t myapp:v1 . -> Option A

4. Quick Check:

   docker build -t name:tag . [OK]

Hint: Use -t before name:tag and end with build context [OK]

Common Mistakes:

• Omitting -t option
• Using incorrect flags like -name
• Placing tag after context

3. What will be the output of the command docker images after running docker build -t testapp:latest . successfully?

medium

A. An error message about missing tag

B. No new images listed

C. A container named testapp running

D. An image named testapp with tag latest listed

Solution

1. Step 1: Understand what docker build -t testapp:latest . does

   This command builds an image and tags it as testapp:latest.

2. Step 2: Check what docker images shows

   The docker images command lists all images including the newly built one with its name and tag.

3. Final Answer:

   An image named testapp with tag latest listed -> Option D

4. Quick Check:

   Build tags appear in docker images [OK]

Hint: Built images show up with their tags in docker images list [OK]

Common Mistakes:

• Expecting containers to appear in images list
• Thinking build fails without explicit tag
• Confusing image and container outputs

4. You run docker build -t myimage: . but get an error saying "invalid reference format". What is the most likely cause?

medium

A. The build context path is incorrect

B. The Dockerfile is missing in the directory

C. The tag name is missing a tag part after colon

D. The image name contains uppercase letters

Solution

1. Step 1: Analyze the error message "invalid reference format"

   This error usually means the image name or tag format is wrong.

2. Step 2: Check the command docker build -t myimage: .

   myimage: has a colon but no tag after it, causing the "invalid reference format" error.

3. Step 3: Identify the most common cause

   The most common cause is a missing tag after colon in the tag name, causing invalid format.

4. Final Answer:

   The tag name is missing a tag part after colon -> Option C

5. Quick Check:

   Tag must be after colon, else invalid format error [OK]

Hint: Check for colon without tag in image name [OK]

Common Mistakes:

• Assuming missing Dockerfile causes this error
• Confusing build context errors with tag format
• Thinking uppercase letters cause invalid format

5. You want to build a Docker image from a Dockerfile in ./app directory and tag it with two tags: myapp:1.0 and myapp:latest. Which command correctly does this in one build?

hard

A. docker build -t myapp:1.0 ./app && docker tag myapp:1.0 myapp:latest

B. docker build -t myapp:1.0 -t myapp:latest ./app

C. docker build --tag myapp:1.0 ./app && docker build --tag myapp:latest ./app

D. docker build -t myapp:1.0:latest ./app

Solution

1. Step 1: Understand how to tag multiple tags in one build

   Docker allows multiple -t options in one build command to assign multiple tags.

2. Step 2: Analyze the options

   docker build -t myapp:1.0 -t myapp:latest ./app uses two -t flags in one command, which is correct. docker build -t myapp:1.0 ./app && docker tag myapp:1.0 myapp:latest uses two commands, which works but is two steps, not one. docker build --tag myapp:1.0 ./app && docker build --tag myapp:latest ./app runs two builds, inefficient. docker build -t myapp:1.0:latest ./app uses invalid tag format.

3. Final Answer:

   docker build -t myapp:1.0 -t myapp:latest ./app -> Option B

4. Quick Check:

   Use multiple -t flags to tag once [OK]

Hint: Use multiple -t flags in one build command [OK]

Common Mistakes:

• Trying to combine tags with colon in one string
• Running multiple builds instead of tagging once
• Using incorrect flag names like --tag