Azure Container Instance terminated but the container is still transitioning

Question

Azure Container Instance terminated but the container is still transitioning

Toby 0

I found another question in here (same title, I copied it from there), from September of 2023, when this was apparently a known issue and fix was in progress.

I have an Azure Container Group that contains a single image with a single console application that starts, does some work, then terminates. This has been working perfectly for some time (> 1 year), but in the past week it has twice gotten stuck in this state where it shows as being terminated, but any attempt to start it fails with a message that the container is still transitioning.

Is this again a known issue? Is a fix in progress? What is the root cause, and is there a workaround I can do in my process to avoid it?

Note that the Container Group appears to be terminated, so it can't be stopped through the portal, but it can be force stopped through the AZ CLI. This is not a solution, however, because this process normally launches automatically using a Function App with a Timer Trigger.

Toby 0 Reputation points

2025-03-20T12:53:42.16+00:00

I've already found and tried all of those things, except for opening a support ticket.

I can't deploy to a different region due to corporate policies and how our IaC is set up. All of our services (for each deployment) are in a single Resource Group & Subscription, and our Subscriptions are tied to regions.

This process has been running without a hitch for over a year and suddently quit working last week. I'm just looking to find out if there's a known cause. A specific version of a certain NuGet package that has a known issue, for instance.

Since this was a known issue before (Sep '23), there's got to be somebody out there that knows what caused the issue last time and how it was addressed. That's the information I'm looking for.
Markapuram Sudheer Reddy 1,670 Reputation points Microsoft External Staff

2025-03-21T16:17:40.1833333+00:00

Hi Toby,

Could you please share the activity log of container instance logs and share error code screenshot if exist for more detail to check more about the issue to troubleshoot better.

Check once if any resource constraints causing this issue.

If you have configured a Log Analytics workspace, use the sql query ContainerEvent_CL | limit 50 to check for container events

https://learn.microsoft.com/en-us/azure/container-instances/container-instances-log-analytics#view-logs

If you have any queries, please do let us know, we will help you.

1 answer

Your answer

Toby 0 Reputation points

2025-03-20T12:53:42.16+00:00

I've already found and tried all of those things, except for opening a support ticket.

I can't deploy to a different region due to corporate policies and how our IaC is set up. All of our services (for each deployment) are in a single Resource Group & Subscription, and our Subscriptions are tied to regions.

This process has been running without a hitch for over a year and suddently quit working last week. I'm just looking to find out if there's a known cause. A specific version of a certain NuGet package that has a known issue, for instance.

Since this was a known issue before (Sep '23), there's got to be somebody out there that knows what caused the issue last time and how it was addressed. That's the information I'm looking for.
Markapuram Sudheer Reddy 1,670 Reputation points Microsoft External Staff

2025-03-21T16:17:40.1833333+00:00

Hi Toby,

Could you please share the activity log of container instance logs and share error code screenshot if exist for more detail to check more about the issue to troubleshoot better.

Check once if any resource constraints causing this issue.

If you have configured a Log Analytics workspace, use the sql query ContainerEvent_CL | limit 50 to check for container events

https://learn.microsoft.com/en-us/azure/container-instances/container-instances-log-analytics#view-logs

If you have any queries, please do let us know, we will help you.

Answer 1

Hi Toby,

The discrepancy you are facing now as it had not happened earlier can sometimes likely tied to changes in Azure's infrastructure or operational policies and you don't want to follow the workaround for a resolution by trying to stop and start, as the process normally launches automatically using a Function App to periodically start container instances.

If possible, check once the availability and quota limits of Azure Container Instances compute, memory, and storage resources in Azure regions and by target operating system. https://learn.microsoft.com/en-us/azure/container-instances/container-instances-resource-and-quota-limits

Please check the similar issue workaround here for more detailed information as here it was suggested it was an issue in Microsoft. https://stackoverflow.com/questions/77187248/azure-container-instance-is-still-transitioning-please-retry-later

https://learn.microsoft.com/en-us/troubleshoot/azure/azure-container-instances/configuration-setup/container-group-transitioning-state

If the information is helpful, please click on "Upvote"

If you have any queries, please do let us know, we will help you.

Share via

Azure Container Instance terminated but the container is still transitioning

1 answer

Your answer