Container Apps - ContainerCreateFailure with overlay filesystem mount failure on host node

Hi @raj

Thank you for reaching out to Microsoft Q&A.

This issue occurred due to an Azure Container Apps infrastructure-level failure on the underlying host node, where the container runtime failed during the container creation phase. The container repeatedly crashed with an overlay filesystem mount error (exit code 32), which occurs before the application starts and is unrelated to application code, container image, or configuration. Azure kept scheduling the revision on the same unhealthy node, resulting in a continuous crash loop for approximately 25 minutes. Once the container was forced to run on a different node, the application recovered immediately. This behavior confirms the issue was caused by a platform-side host/node failure in Azure infrastructure, not a customer misconfiguration or deployment change. Such mount and OCI runtime failures during startup are recognized Azure Container Apps platform issues.

Refer below points to resolve this issue or this is the workaround

Create a new revision to force rescheduling

• Create a new container app revision (no code or config change required).
• This forces Azure to place the workload on a different, healthy node.
• Application recovers immediately after rescheduling.

Validate logs and failure type

• Check revision system logs for ContainerCreateFailure, overlay filesystem, or mount exit code 32.
• Confirms failure occurred at infrastructure/runtime level, not application level.

Create a Ticket with Issue Type Billing:

This is a technical support queue, create a new Azure Support Request with issue type as Billing so the Billing team could help you.