ACI does not create due to internalServerError

Question

Hi my ACI creation via yaml fails. All i get is this:

(InternalServerError) Encountered an internal server error. The tracking activity id is '78c244c0-eac4-4b8b-a015-1ef6b9714fae', correlation id is '1ebbf651-e952-4c4a-a4e1-36aadc897a7e'.

Code: InternalServerError

Message: Encountered an internal server error. The tracking activity id is '78c244c0-eac4-4b8b-a015-1ef6b9714fae', correlation id is '1ebbf651-e952-4c4a-a4e1-36aadc897a7e'.

Verbose is no help. What to do?

Answer 1

Hi @David Fabian Schöggl ,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

From what I understood, you are facing intermitent issues while working with ACI instances.

There are some situations that you may are experiencing limits on the requests, or limitation on Azure container services.

Please check the documentation below to better understand limits.

https://learn.microsoft.com/en-us/azure/container-instances/container-instances-resource-and-quota-limits.

Some other interesting docs - https://learn.microsoft.com/en-us/azure/reliability/reliability-containers

Also please using Azure Log Analytics, to monitor your environement to identiy possible issues.

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

Regarding availability, if you are looking for reliability and resilience when delivering your service. I would like to recommend to use AKS cluster (kubernetes), as ACI instances don't garantee high SLA and the infrastructure can change as needed, following Microsoft monitoring systems.

SLA: https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1

WORKAROUND

In the other hand, if you identify any issues with container instance being not stable, the recommendation is to STOP/START the ACI group, this will change the instances running in a specific cluster, moving the instances to another CLuster that are more stable and healty from monitoring perspective.

If the issue still happening, please reach out to our MS support team, opening a ticket and we will work on it.

If it was helpful, please click "Upvote or ACCEPT the Answer" on this post to let us know.

Thank You.

Lisboa