Azure Container App creation fail with operation expired

2025-02-20T19:05:45.9333333+00:00

I create azure container app but it failed with operation expire. No revision created so I cannot see log.

I have no clue where I can check detail of error.

Do you have any idea?

Azure Container Apps
Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
562 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Arko 335 Reputation points Microsoft External Staff
    2025-03-07T09:50:08.7433333+00:00

    Hi Limopasit, Anattapol (Allianz Technology),

    In order to create an Azure Container App, under your resource group create an environment

    
    az containerapp env create \
    
      --name arkorg-env \
    
      --resource-group arkorg \
    
      --location centralindia
    
    

    enter image description here

    Check if the environment was created successfully

    
    az containerapp env show --name arkorg-env --resource-group arkorg
    
    

    enter image description here

    Now deploy your container app. I am deploying in Nginx on it

    
    az containerapp create \
    
      --name mycontainerapp \
    
      --resource-group arkorg \
    
      --environment arkorg-env \
    
      --image nginx \
    
      --target-port 80 \
    
      --ingress external \
    
      --cpu 0.5 \
    
      --memory 1.0Gi
    
    

    enter image description here

    Check the container app's status

    enter image description here

    Looks good.

    fetch the URL and test it out

    
    az containerapp show --name mycontainerapp --resource-group arkorg --query "properties.configuration.ingress.fqdn" --output tsv
    
    

    enter image description here

    enter image description here

    Works fine.

    If the deployment fails with operation expired, proceed to troubleshooting.

    Check logs if revision exists

    
    az containerapp logs show --name mycontainerapp --resource-group arkorg
    
    

    enter image description here

    Check for activity logs-

    
    az monitor activity-log list --resource-group arkorg
    
    

    enter image description here

    If no revision exists, the issue is likely image pull failure or resource quota limits.

    If CPU/memory is maxed out, try a different region

    If operation is failing because of image pull issue then let me know if you are using a private container registry?

    If so , update your aca with the private acr using it's username and password

    
    az containerapp update \
    
      --name mycontainerapp \
    
      --resource-group arkorg \
    
      --image myregistry.azurecr.io/myimage:v1 \
    
      --registry-server myregistry.azurecr.io \
    
      --registry-username <USERNAME> \
    
      --registry-password <PASSWORD>
    
    

    MS Doc- Troubleshoot container create failures in Azure Container Apps | Microsoft Learn

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.