Azure Container Instances (ACI) for simple runs - Step-by-Step Execution

Process Flow - Azure Container Instances (ACI) for simple runs

Create Container Group

↓

Specify Container Image

↓

Set CPU and Memory

↓

Configure Networking

↓

Deploy Container Instance

↓

Container Starts Running

↓

Container Completes or Stops

↓

View Logs or Output

↓

Delete Container Instance

This flow shows how you create and run a simple container in Azure Container Instances, from setup to cleanup.

Execution Sample

Azure

az container create --resource-group myGroup --name mycontainer --image mcr.microsoft.com/azuredocs/aci-helloworld --cpu 1 --memory 1 --restart-policy Never

This command creates and runs a container instance with 1 CPU and 1 GB memory, using a simple hello world image.

Process Table

Step	Action	Input/Config	Result/State
1	Create container group	Resource group: myGroup, Name: mycontainer	Container group created, ready to deploy
2	Specify container image	Image: mcr.microsoft.com/azuredocs/aci-helloworld	Image set for container
3	Set CPU and memory	CPU: 1, Memory: 1 GB	Resources allocated
4	Set restart policy	Restart policy: Never	Container will not restart after exit
5	Deploy container instance	Run deployment command	Container instance starts running
6	Container runs	Container executes hello world app	Container status: Running
7	Container completes	App finishes execution	Container status: Terminated
8	View logs	az container logs --resource-group myGroup --name mycontainer	Output: Hello from Azure Container Instances!
9	Delete container	az container delete --resource-group myGroup --name mycontainer	Container instance deleted

💡 Container completes execution and is deleted to free resources

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	After Step 7	Final
Container Group	None	Created	Created	Running	Terminated	Deleted
Container Image	None	Set to hello world image	Set	Set	Set	Set
CPU	None	None	1 CPU	1 CPU	1 CPU	None
Memory	None	None	1 GB	1 GB	1 GB	None
Restart Policy	None	None	Never	Never	Never	None
Container Status	None	None	None	Running	Terminated	Deleted

Key Moments - 3 Insights

Why does the container stop running after the app finishes?

Because the restart policy is set to 'Never', the container stops once the app completes, as shown in step 7 of the execution table.

What happens if you don't delete the container instance after it finishes?

The container instance remains in the terminated state and continues to consume resources and cost until deleted, so step 9 is important.

How do you see what the container printed during its run?

You use the 'az container logs' command as in step 8 to view the container's output logs.

Visual Quiz - 3 Questions

Look at the execution table, what is the container status immediately after deployment (step 5)?

A Deleted

B Terminated

C Running

D Created

💡 Hint

Check the 'Result/State' column at step 5 in the execution table.

At which step does the container stop running?

A Step 7

B Step 6

C Step 8

D Step 9

💡 Hint

Look for when the container status changes to 'Terminated' in the execution table.

If you change the restart policy to 'Always', what would change in the execution table?

A Container would never start running

B Container status would stay 'Running' after step 7

C Container would be deleted automatically

D Logs would not be available

💡 Hint

Consider how restart policy affects container status after app completion.

Concept Snapshot

Azure Container Instances (ACI) let you run containers easily without managing servers.
Use 'az container create' with image, CPU, memory, and restart policy.
Container runs until app finishes or restart policy triggers.
View logs with 'az container logs'.
Delete container to free resources.

Full Transcript

This visual execution shows how to run a simple container in Azure Container Instances (ACI). First, you create a container group and specify the container image. Then you set CPU and memory resources and choose a restart policy. Deploying the container starts it running. The container runs the app and then stops if the restart policy is 'Never'. You can view the container's output logs and finally delete the container instance to free resources. Key points include understanding the restart policy effect and the importance of deleting containers after use.