Master Azure Container Instances (ACI) and Restart Policies

Azure Container Instances (ACI) are the "speed demons" of the Azure cloud. If you need to run a containerized application without the overhead of managing Virtual Machines or the complexity of Kubernetes, ACI is your go-to service. In this recap, we’ll walk through how to deploy a web server, benchmark it using a task-oriented container, and understand how to scale your resources effectively. 1. Authenticating and Setting the Stage Before deploying, you must connect your terminal to your Azure subscription. Using the Azure CLI is the fastest way to interact with ACI. # Log in using your browser az login --use-device-code # Save your Resource Group name to a variable for easy use rg = $( az group list --query "[].name" --output tsv ) 2. Deploying Your First Container We start by deploying a simple "Hello World" web server. Unlike a VM, which might take minutes to boot, ACI starts in seconds. The Command: az container create --resource-group $rg \ --name calabscontainer \ --image gcr.io/