Search code examples
azureazure-container-service

Cannot create Azure Service Container

I tried to create an Azure Service Container in the UK West region. I went through all the steps without issue however once I clicked 'Create' after a few moments I was met with :

LocationNotAvailableForResourceTypeThe provided location 'ukwest' is not available for resource type 'Microsoft.ContainerService/containerServices'. List of available regions for the resource type is 'japaneast,centralus,eastus2,japanwest,eastasia,southcentralus,australiaeast,australiasoutheast,brazilsouth,southeastasia,westus,northcentralus,westeurope,northeurope,eastus'.

Okay, I realised that was my mistake and went on to create the container in West Europe.

Now when I attempt to create the container I am met with the same error, despite setting the location to West Europe.

I have tried :

  1. Hard refreshing and going through the whole process again.
  2. Clearing my web cache and going through the whole process again.
  3. Opening an incognito window and going through the whole process again.

I have also ensured that the Azure Container Service and Azure Container Registry are registered on my subscription ID. Initially the resource group I was attempting to deploy on was set to UK West, however after deleting and recreating on West Europe, I still am unable to create the service container.

Update:

I have had Microsoft Azure Support on this case. It looks like there is an issue whereby my subscription ID cannot create the service container in the West Europe region. This has been referred onto the technical team. I'll post the solution here when I receive it.

Solution

  • Ok, So I've had MSFT Support on this with me for a couple weeks. The solution!

    I had a dns that you couldn't use. Even though it passes through all validation checks telling me that it's fine the deployment failed.

    Changed the dns and it's fine.

    So to summarise all the things you need to do, which it doesn't state anywhere:

    • Make sure you have registered Azure Container Service and Azure Container Registry on your subscription ID.

    • Make sure you are deploying to a region that actually supports your feature, not only that make sure your resource group is located in the same valid region. (It allows you to pass through all validation selecting a resource group that is in an invalid region)

    • Make sure your resource group hasn't been created by a previous failed deployment.

    • Attempt to change your dns to something else, it might be invalid somehow. Although it will not tell you this, just fail the deployment.

    • Essentially do not trust the validation on Azure at all. It'll tell you you're able to do things and everything is fine, when in fact it isn't.

    I'll edit this answer with any further relevant update I receive.