az containerapp update: Roll Out Container Apps in CI

Update an Azure Container App, typically rolling to a new container image.

az containerapp update changes a Container App, most often to deploy a new image, which creates a new revision. In CI you push an image to ACR, then update the app to that tag. Flags also let you adjust env vars and scaling.

Common flags

-n NAME and -g RESOURCE_GROUP - target app
--image IMAGE - new container image
--set-env-vars KEY=VALUE - set or update env vars
--revision-suffix SUFFIX - label the new revision

Example in CI

Roll the app to a freshly pushed image tag.

shell

az containerapp update \
  -n my-app -g my-rg \
  --image myregistry.azurecr.io/app:${GITHUB_SHA}

Common errors in CI

ContainerAppOperationError: ... failed provisioning state - new revision crashed on startup
ERROR: ... was not found - wrong app name or resource group
UNAUTHORIZED: ... registry - Container App cannot pull the image (registry credentials/managed identity)

Key takeaways

Updates a Container App and creates a new revision, commonly for a new image.
Ensure the app can pull from ACR (registry creds or managed identity).
A failed revision usually means the container crashed on startup.