Azure Container App Revisions Time Out In Status "Activating"

Paul Voelker 5 Reputation points


I have an Azure Container App that fails at revision deployment.
In the "Revisions and replicas" the current revision hangs in the Running status "Activating" until timing out eventually and switching to status "Degraded".

This started to happen without any changes to the image that the Container App runs on, or any changes in general. Also older revisions that worked at some point behave the same when I try to activate these.

I can download the image from the linked ACR repository with the exact config that is used by the Container App and run it locally, so I'm pretty sure that this is not an issue with my image. It seems like no container is ever started.

The system log stream and ContainerAppSystemLogs_CL are attached. They state that the image was pulled successfully and then the timeout.

Also I noticed that Container App Jobs using the same image but also the ones from a different resource group that use a kind of similar but separate and older image from a separate ACR repository started to fail in the same way at the same time. The System Logs show PulledImage and then DeadlineExceeded after an hour (the configured timeout of these container app jobs).

How do I debug this problem? Could it be a quota limit?

Any help is greatly appreciated!

Screenshot 2024-07-01 at 13.35.46

Screenshot 2024-07-01 at 13.11.35

Screenshot 2024-07-01 at 13.09.53

Query Data (1).txt

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