Tagging images during build in Docker - Commands & Configuration

Introduction

When you build a Docker image, you want to give it a name and a version so you can find and use it later. Tagging images during build helps you label your images clearly, so you know what they are and which version they are.

When you want to save a specific version of your app image to use later or share with others.

When you need to run multiple versions of the same app on your machine or server.

When you want to push your image to a registry with a clear name and version.

When you want to avoid confusion between different builds of your app.

When you want to automate builds and keep track of image versions in CI/CD pipelines.

Commands

This command builds a Docker image from the current folder (.) and tags it with the name 'my-app' and version '1.0'. The -t flag sets the tag.

Terminal

docker build -t my-app:1.0 .

Expected Output

Sending build context to Docker daemon  2.048kB

Step 1/3 : FROM alpine:3.18

3.18: Pulling from library/alpine

Digest: sha256:...

Status: Downloaded newer image for alpine:3.18

 ---> 3f53bb00af94

Step 2/3 : RUN echo "Hello, Docker!"

 ---> Running in 123abc456def

Removing intermediate container 123abc456def

 ---> 789xyz123uvw

Step 3/3 : CMD ["echo", "Hello, Docker!"]

 ---> Running in 456def789abc

Removing intermediate container 456def789abc

 ---> 321uvw654xyz

Successfully built 321uvw654xyz

Successfully tagged my-app:1.0

→

-t - Assigns a name and optionally a tag in the 'name:tag' format to the image.

This command lists all Docker images with the name 'my-app' so you can see the tagged image you just built.

Terminal

docker images my-app

Expected Output

REPOSITORY   TAG     IMAGE ID       CREATED          SIZE

my-app       1.0     321uvw654xyz   10 seconds ago   5.6MB

This runs the Docker image tagged 'my-app:1.0' to verify it works as expected. The --rm flag removes the container after it stops.

Terminal

docker run --rm my-app:1.0

Expected Output

Hello, Docker!

→

--rm - Automatically removes the container when it exits to keep your system clean.

Key Concept

If you remember nothing else from this pattern, remember: use the -t flag during docker build to give your image a clear name and version tag.

Common Mistakes

Building the image without the -t flag and then trying to run it by name.

Without a tag, the image has no name, so you cannot easily find or run it by name.

Always use the -t flag with a name and tag when building images to identify them.

Using a tag with spaces or invalid characters.

Docker tags must not contain spaces or special characters, causing build errors.

Use only letters, numbers, dots, dashes, and underscores in tags.

Summary

Use 'docker build -t name:tag .' to build and tag your image in one step.

Check your tagged images with 'docker images name' to confirm the tag.

Run your tagged image with 'docker run name:tag' to test it.

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