ACR image building and pushing in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to log in to Azure Container Registry (ACR).

Azure

az acr [1] --name myRegistry

Drag options to blanks, or click blank then click option'

Apush

Blogin

Cbuild

Dcreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'push' instead of 'login' will try to push an image without authentication.

Using 'build' or 'create' does not log you in.

The az acr login command logs you into your Azure Container Registry so you can push or pull images.

2fill in blank

medium

Complete the command to build a Docker image and push it to ACR in one step.

Azure

az acr [1] --registry myRegistry --image myapp:v1 .

Drag options to blanks, or click blank then click option'

Acreate

Bpush

Clogin

Dbuild

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'push' alone requires the image to be built first.

Using 'login' or 'create' does not build images.

The az acr build command builds a Docker image from your source code and pushes it to your Azure Container Registry automatically.

3fill in blank

hard

Fix the error in the command to push a local Docker image to ACR.

Azure

docker [1] myRegistry.azurecr.io/myapp:v1

Drag options to blanks, or click blank then click option'

Apush

Bbuild

Clogin

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'build' tries to create an image instead of uploading.

Using 'login' is for authentication, not pushing.

Using 'run' starts a container, not pushes an image.

The docker push command uploads your local image to the specified container registry.

4fill in blank

hard

Fill both blanks to tag a local Docker image before pushing it to ACR.

Azure

docker tag [1] [2]

Drag options to blanks, or click blank then click option'

Amyapp:latest

BmyRegistry.azurecr.io/myapp:v1

Cmyapp:v1

DmyRegistry.azurecr.io/myapp:latest

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the order of arguments causes tagging errors.

Using 'latest' tag inconsistently can confuse which image is pushed.

You tag your local image (e.g., myapp:v1) with the full registry path (myRegistry.azurecr.io/myapp:v1) before pushing it.

5fill in blank

hard

Fill all three blanks to build, tag, and push a Docker image to ACR manually.

Azure

docker [1] -t [2] . && docker [3] [2]

Drag options to blanks, or click blank then click option'

Abuild

BmyRegistry.azurecr.io/myapp:v2

Cpush

Drun

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'run' instead of 'push' uploads nothing.

Forgetting to tag the image before pushing causes errors.

First, you build the image with docker build and tag it with the registry path. Then, you push it with docker push.

Practice

1. What is the primary purpose of the az acr build command in Azure Container Registry (ACR)?

easy

A. To run a container instance in Azure

B. To delete an image from ACR

C. To create a new Azure Container Registry

D. To build a container image and push it directly to ACR

Solution

1. Step 1: Understand the command purpose

   The az acr build command is designed to build container images from a Dockerfile and push them to an Azure Container Registry.

2. Step 2: Compare options with command function

   Options A, B, and C describe other unrelated actions like deleting images, creating registries, or running containers, which are not the purpose of az acr build.

3. Final Answer:

   To build a container image and push it directly to ACR -> Option D

4. Quick Check:

   az acr build = build and push image [OK]

Hint: Remember: az acr build builds and pushes images [OK]

Common Mistakes:

• Confusing build with delete or create registry commands
• Thinking az acr build runs containers
• Assuming it only builds locally without pushing

2. Which of the following is the correct syntax to build and push an image named myapp:v1 to an Azure Container Registry named myregistry using az acr build?

easy

A. az acr build --registry myregistry --image myapp:v1 .

B. az acr build --image myapp:v1 --registry myregistry

C. az acr build --name myregistry --tag myapp:v1 .

D. az acr build --push --image myapp:v1 --registry myregistry

Solution

1. Step 1: Identify correct parameter order and names

   The correct syntax uses --registry to specify the registry, --image for image name and tag, followed by the build context path (here . for current directory).

2. Step 2: Validate options

   az acr build --image myapp:v1 --registry myregistry omits the required build context path (.). az acr build --registry myregistry --image myapp:v1 . matches the correct syntax. az acr build --name myregistry --tag myapp:v1 . uses incorrect flags --name and --tag which are invalid. az acr build --push --image myapp:v1 --registry myregistry uses --push which is not a valid flag for az acr build.

3. Final Answer:

   az acr build --registry myregistry --image myapp:v1 . -> Option A

4. Quick Check:

   Correct flags: --registry, --image, context path [OK]

Hint: Use --registry then --image followed by context path [OK]

Common Mistakes:

• Using --name instead of --registry
• Adding unsupported flags like --push
• Omitting the build context path

3. Given the command:

az acr build --registry myregistry --image sampleapp:latest ./app

What will happen after this command runs successfully?

medium

A. The image sampleapp:latest is pulled from myregistry and run locally

B. The Dockerfile in ./app is built into an image tagged sampleapp:latest and pushed to myregistry

C. A new Azure Container Registry named sampleapp is created

D. The local Docker daemon builds the image but does not push it

Solution

1. Step 1: Understand the command behavior

   The az acr build command builds the Dockerfile found in the specified path (./app) and pushes the resulting image to the specified Azure Container Registry (myregistry) with the given tag (sampleapp:latest).

2. Step 2: Eliminate incorrect options

   The image sampleapp:latest is pulled from myregistry and run locally describes pulling and running, which az acr build does not do. A new Azure Container Registry named sampleapp is created talks about creating a registry, which requires a different command. The local Docker daemon builds the image but does not push it suggests local build only, but az acr build builds in Azure and pushes automatically.

3. Final Answer:

   The Dockerfile in ./app is built into an image tagged sampleapp:latest and pushed to myregistry -> Option B

4. Quick Check:

   az acr build builds and pushes image [OK]

Hint: az acr build builds remotely and pushes automatically [OK]

Common Mistakes:

• Thinking image is only built locally
• Confusing build with run or pull
• Assuming registry is created automatically

4. You run the command:

az acr build --registry myregistry --image myapp:v2 ./src

but get an error saying Dockerfile not found. What is the most likely cause?

medium

A. The image tag myapp:v2 is invalid

B. The registry name myregistry is incorrect

C. The ./src directory does not contain a Dockerfile

D. You forgot to login to Azure CLI

Solution

1. Step 1: Analyze the error message

   The error Dockerfile not found means the build context directory (./src) does not have a Dockerfile, which is required to build the image.

2. Step 2: Check other options

   Incorrect registry or image tag would cause different errors. Forgetting to login would cause authentication errors, not missing Dockerfile.

3. Final Answer:

   The ./src directory does not contain a Dockerfile -> Option C

4. Quick Check:

   Missing Dockerfile = Dockerfile not found error [OK]

Hint: Ensure Dockerfile exists in build context folder [OK]

Common Mistakes:

• Assuming registry or tag causes Dockerfile error
• Ignoring the build context path
• Not verifying Dockerfile presence before build

5. You want to build and push multiple images with tags v1 and latest for your app using az acr build. Which approach correctly achieves this in a single command?

hard

A. Use --image myapp:v1 --image myapp:latest with the build context path

B. Run az acr build twice, once for each tag

C. Use --tag v1,latest with the image name

D. Build locally twice and push manually

Solution

1. Step 1: Understand multi-tag build syntax

   The az acr build command supports specifying multiple --image flags to tag the same build with different tags in one command.

2. Step 2: Evaluate options

   Use --image myapp:v1 --image myapp:latest with the build context path correctly uses multiple --image flags. Run az acr build twice, once for each tag works but is two commands, not single. Use --tag v1,latest with the image name uses an invalid --tag flag. Build locally twice and push manually is manual and not a single command.

3. Final Answer:

   Use --image myapp:v1 --image myapp:latest with the build context path -> Option A

4. Quick Check:

   Multiple --image flags tag multiple images [OK]

Hint: Use multiple --image flags to tag in one build [OK]

Common Mistakes:

• Trying to use --tag with multiple tags
• Running separate builds unnecessarily
• Building locally instead of using az acr build