question

17323040 avatar image
0 Votes"
17323040 asked AndrewShepherd commented

Container Instance stuck in "Pending" status

I try to create Azure Container Instance from ARM template which I used previously.
Deployment says that instance is "Created" but when I go to that instance I see that it is in state "Pending" and for all containers there are no any events - so images was not even tried to be downloaded.

Same happens with other subscription and diferent region.
I do not see any problem with Azure Health Service - so wondering how I could see what is the problem with my deployments?

Update:
We are deployed ARM template through
https://portal.azure.com/#create/Microsoft.Template
using Custom deployment.
So it has nothing to do with k8s.


Update2:
Also it seams that MS has now issue https://app.azure.com/h/KKYB-RSZ/ but in description of that issue mentioned Service Buses and Storage account and NOT ACI

Update3:

There are no any init containers or volumes. I have tried to add Liveness check - but result is same with and without it.

 $ az container attach --resource-group test --container-name moc --name ox_env  --subscription C
 Container 'moc' is in state 'Unknown'...

And here are some screenshots from Portal:
133171-dbnectm3e1.png
133172-wg2igz8bvr.png
133116-kssebx9kxo.png
On second screenshot you could see "No events found in the last few hours" - that message was there all the time!


azure-container-instances
dbnectm3e1.png (50.0 KiB)
wg2igz8bvr.png (68.1 KiB)
kssebx9kxo.png (107.4 KiB)
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@17323040 , The container group is waiting for infrastructure setup, such as a node assignment, virtual network provisioning, initialize (finish running init containers, mount Azure file volumes if applicable) or anything else needed prior to pulling the user image. [Reference] Have you noticed transition of the container(s) to any other state? Can you please share if anything can be found from the relevant checks mentioned here? Also can you please share the output from az container attach --resource-group $ResourceGroup --name $ContainerName? Note: Please redact any sensitive information before sharing with us here.

0 Votes 0 ·

I am having this problem as well, in the AustraliaEast region.

I had a project two years ago where one container would programmatically start up a container instance to perform a media-encoding job. This worked reliably, but we didn't go ahead with it in production.

Two years later I am running it again, and it doesn't reliably run. The container group just gets stuck in the 'creating' or 'updating' phase. It might run, but several hours after being asked to.

Is Azure having a stability problem with the Container Instance service?

https://josefbajada.medium.com/8-reasons-why-azure-container-instances-suck-a8a81fa91f92#1b63

0 Votes 0 ·

1 Answer

learn2skills avatar image
0 Votes"
learn2skills answered 17323040 commented

Hi @17323040

Please check on the below url it is explained.

When you deploy Pods to ACI through Kubernetes, you may recognize that all Pods stuck in state Pending when they’re meant to be deployed to the aci-connector node (aci-connector is the default name for the ACI node). You may ask why all pods stuck at this stage. To get more insights let us examine the cluster a bit
https://www.thorsten-hans.com/fix-pods-stuck-in-pending-on-azure-container-instances/



If the Answer is helpful, please click Accept Answer and up-vote, so that it can help others in the community looking for help on similar topics.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

We does not work with ACI through Kubernetes. I have updated my question.

0 Votes 0 ·