Deployment scripts failing when requesting container instance in westeurope

Viktor Einarsson 6 Reputation points
2022-09-29T13:24:56.04+00:00

We just started receiving errors on Friday from ARM template deployments that are trying to run deployment scripts (which apparently use container instances behind the scenes). This has been an issue this entire week as well. I´m not sure if this is right place to ask question but I´m out of options.

The error that we receive is the following:

"{
"status": "failed",
"error": {
"code": "DeploymentScriptContainerInstancesServiceUnavailable",
"message": "The requested resource is not available in the location 'westeurope' at this moment. Please retry with a different resource request or in another location. Resource requested: '1' CPU '1' GB memory 'Linux' OS"
}
}"

We would occasionally receive this error and a simple retry would fix it but now we cannot get past this error. Our entire infrastructure deployment is failing due to this.

Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
633 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. shiva patpi 13,131 Reputation points Microsoft Employee
    2022-09-30T01:23:03.417+00:00

    Hello @Viktor Einarsson ,
    Normally that error happens if underlying compute resources are running low but it can be retried, I just tried creating a container instance in west Europe and it went through fine!
    Can you kindly retry from your end now?

  2. KarishmaTiwari-MSFT 18,352 Reputation points Microsoft Employee
    2022-10-18T22:29:48.85+00:00

    Based on the conversation with the customer as well as internally tracking the support case created by the customer, here is the latest update if anyone else is facing this issue -

    ARM template deployments for creating Azure container instances are not working as expected in few regions and west Europe is one of them. The product team is working on a fix.
    We will share an update here once the issue is fixed.