Is there an issue with container instance creation in AustraliaEast starting as of yesterday?

Derek H 96 Reputation points
2020-06-05T00:50:09.017+00:00

Hi,

I have a customer's container and registry in the Australia East region, and until yesterday (after months of working) we were provisioning an image based on mcr.microsoft.com/dotnet/framework/runtime:4.8-windowsservercore-ltsc2019, with the properties below.

Before asking this, I also tried CPU and memory of 2 each based on the updated values provided on https://learn.microsoft.com/en-us/azure/container-instances/container-instances-region-availability (which must have downgraded the capabilities since we deployed this because 4-CPU and 4-Ram was working) but we were getting the same error as below. Can someone shed some light on this as we need this container to be created every 2 hours to run an integration I don't want to continue to be throwing up instances on East US given the data transfer and data transfer cost as the container registry is still in Australia East.

Error:
The requested resource is not available in the location 'australiaeast' at this moment. Please retry with a different resource request or in another location. Resource requested: '2' CPU '2' GB memory 'Windows Server 2019 - Before 2B' OS

Container Instance Config:

[
{
"name": "<redacted>",
"properties": {
"image": "<redacted>",
"resources": {
"requests": {
"memoryInGB": 4,
"cpu": 4
},
"limits": {
"memoryInGB": 4,
"cpu": 4
}
},
"ports": [
{
"protocol": "TCP",
"port": 80
}
],
"environmentVariables": [
{
"name": "<redacted>",
"value": "<redacted>"
},
{
"name": "<redacted>",
"value": "<redacted>"
},
{
"name": "<redacted>",
"value": "<redacted>"
}
]
}
}
]

Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
645 questions
{count} votes

Accepted answer
  1. Derek H 96 Reputation points
    2020-06-23T02:03:45.78+00:00

    Azure Support on Twitter gave us a free support case... Basically the base windows/.net image we were using was too old (there are before2b and after2b images... The beforeb2 images are being retired/lessened capacity as anything before2b had a security hole, therefore everyone must transition base images to one using an after 2b image (list the cached images on azure to see what I mean about before/after 2b.

    Hth
    Derek


0 additional answers

Sort by: Most helpful