Azure Container Instances入門｜VMを作らずにアプリを数分で動かすACIデプロイ手順

この記事のポイント

・az container createコマンド1本でVMなしにコンテナが数分で起動できる
・ACIはバッチ処理・検証・小規模APIで最もコスパが高いコンテナ実行の選択肢
・環境変数・ポート公開・DNSラベルはcreate時のオプションで一括設定する
・az container logsとaz container showで動作確認と障害調査ができる

# add microsoft rpm repository and install azure-cli
sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
sudo dnf install -y https://packages.microsoft.com/config/rhel/9.0/packages-microsoft-prod.rpm
sudo dnf install -y azure-cli

# install azure-cli on ubuntu 22.04 / 24.04 LTS
curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

az version
# output example
{
  "azure-cli": "2.61.0",
  "azure-cli-core": "2.61.0",
  "azure-cli-telemetry": "1.1.0"
}

# open browser and login to azure account
az login

# create resource group in japan east region
az group create \
  --name aci-demo-rg \
  --location japaneast

# output: provisioningState should be "Succeeded"
{
  "id": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/aci-demo-rg",
  "location": "japaneast",
  "name": "aci-demo-rg",
  "properties": {
    "provisioningState": "Succeeded"
  }
}

# create and start a container with public http access
az container create \
  --resource-group aci-demo-rg \
  --name aci-helloworld \
  --image mcr.microsoft.com/azuredocs/aci-helloworld \
  --ports 80 \
  --dns-name-label aci-demo-handson \
  --location japaneast

# show container status, fqdn, and ip address
az container show \
  --resource-group aci-demo-rg \
  --name aci-helloworld \
  --query "{Status:instanceView.state, FQDN:ipAddress.fqdn, IP:ipAddress.ip}"

# output example: running state with public ip
{
  "FQDN": "aci-demo-handson.japaneast.azurecontainer.io",
  "IP": "20.89.xxx.xxx",
  "Status": "Running"
}

# pass environment variables to the container
az container create \
  --resource-group aci-demo-rg \
  --name aci-myapp \
  --image myregistry.azurecr.io/myapp:latest \
  --ports 8080 \
  --dns-name-label aci-myapp-demo \
  --environment-variables \
    APP_ENV=production \
    LOG_LEVEL=info \
  --location japaneast

# use secure env vars for sensitive values (hidden from logs)
az container create \
  --resource-group aci-demo-rg \
  --name aci-myapp \
  --image myregistry.azurecr.io/myapp:latest \
  --ports 8080 \
  --dns-name-label aci-myapp-demo \
  --environment-variables APP_ENV=production \
  --secure-environment-variables DB_PASSWORD=your_secret_here \
  --location japaneast

# create a batch job container: 2 cpu cores, 4GB ram, no restart
az container create \
  --resource-group aci-demo-rg \
  --name aci-batch \
  --image myregistry.azurecr.io/batch-job:latest \
  --cpu 2 \
  --memory 4 \
  --restart-policy Never \
  --location japaneast

# check acr admin credentials before use
az acr credential show --name myregistry --query "{user:username,pass:passwords[0].value}"

# create container from private acr image with registry credentials
az container create \
  --resource-group aci-demo-rg \
  --name aci-private \
  --image myregistry.azurecr.io/myapp:latest \
  --registry-login-server myregistry.azurecr.io \
  --registry-username  \
  --registry-password  \
  --ports 8080 \
  --dns-name-label aci-private-demo \
  --location japaneast

# show stdout/stderr logs from the container
az container logs \
  --resource-group aci-demo-rg \
  --name aci-helloworld

# output example: nginx access log entries
listening on port 80
::ffff:10.240.255.31 - - [18/Jul/2026:06:30:12 +0000] "GET / HTTP/1.1" 200 1663 "-" "Mozilla/5.0 ..."
::ffff:10.240.255.31 - - [18/Jul/2026:06:30:13 +0000] "GET /favicon.ico HTTP/1.1" 200 946 "-" "..."

# tail logs in real time (press Ctrl+C to stop)
az container logs \
  --resource-group aci-demo-rg \
  --name aci-helloworld \
  --follow

# open an interactive bash shell inside the running container
az container exec \
  --resource-group aci-demo-rg \
  --name aci-helloworld \
  --exec-command "/bin/bash"

# check container events to diagnose startup failures
az container show \
  --resource-group aci-demo-rg \
  --name aci-helloworld \
  --query "containers[0].instanceView.events[]"

# output example: successful startup event sequence
[
  {
    "count": 1,
    "firstTimestamp": "2026-07-18T06:28:00+00:00",
    "lastTimestamp": "2026-07-18T06:28:00+00:00",
    "message": "pulling image ...",
    "name": "Pulling",
    "type": "Normal"
  },
  {
    "count": 1,
    "firstTimestamp": "2026-07-18T06:28:45+00:00",
    "lastTimestamp": "2026-07-18T06:28:45+00:00",
    "message": "Started container",
    "name": "Started",
    "type": "Normal"
  }
]

# stop the container to halt billing (can restart later)
az container stop \
  --resource-group aci-demo-rg \
  --name aci-helloworld

# restart a stopped container
az container start \
  --resource-group aci-demo-rg \
  --name aci-helloworld

# delete a specific container (--yes skips confirmation prompt)
az container delete \
  --resource-group aci-demo-rg \
  --name aci-helloworld \
  --yes

# delete the entire resource group and all its resources
az group delete \
  --name aci-demo-rg \
  --yes \
  --no-wait

# check container events for image pull error
az container show \
  --resource-group aci-demo-rg \
  --name aci-helloworld \
  --query "containers[0].instanceView.events[]"

# error example: image not found or wrong tag
{
  "message": "Failed to pull image: mcr.microsoft.com/azuredocs/aci-helloworld:wrong-tag",
  "name": "Failed",
  "type": "Warning"
}