Container 'app_name' was terminated with exit code '132'

Sowndar kumaresan 21 Reputation points
2023-08-25T12:33:28.19+00:00

Hi team, We have provisioned the container app and when we pushed the latest build, the revision was working fine until some time after some time system log showed the application crashed with "Container 'containerAppName' was terminated with exit code '132'"

Can anyone suggest the best way to debug and same container works well in lower environments and the CPU and memory usage also seem to be normal.

for a few minutes application works fine able to get the response after some time if fails. If it might be a memory issue how can we debug the same?

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

Accepted answer
  1. navba-MSFT 16,610 Reputation points Microsoft Employee
    2023-08-30T09:33:12.2966667+00:00

    @Sowndar kumaresan Thanks for getting back and sharing the details. in the non-working ( higher) scenario, Could you please try to **list **the environment variables and check if it has been set correctly ?

    Run the below command and then try to access the FQDN:

    az containerapp revision list \
      --name $CONTAINERAPPS_NAME \
      --resource-group $RESOURCE_GROUP \
      --query "[].{Name:name,DateCreated:createdTime,ProvisionStatus:provisioningState,Traffic:trafficWeight,Active:active,FQDN:fqdn}"
    

    While accessing the FQDN from browser it should list the env variables and its value. See an example below:

    enter image description here

    Awaiting your reply.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful