You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.
The location property specified in the multi-container yml deployment file is ignored. The resulting ACI is always deployed in the default location of the resource group.
The text was updated successfully, but these errors were encountered:
I see the same behavior when using docker-compose.
docker context create aci mycontext --location westeurope
docker context use mycontext
docker compose up
[+] Running 0/1
⠇ Group container_instance_test Waiting 1.8s
containerinstance.ContainerGroupsClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="LocationNotAvailableForResourceType" Message="The provided location 'norwayeast' is not available for resource type 'Microsoft.ContainerInstance/containerGroups'. List of available regions for the resource type is 'westcentralus,westus,eastus,westeurope,westus2,northeurope,southeastasia,eastus2,centralus,australiaeast,uksouth,southcentralus,centralindia,brazilsouth,southindia,northcentralus,eastasia,canadacentral,japaneast,koreacentral,francecentral'."
docker version
Client: Docker Engine - Community
Cloud integration: 1.0.3
Version: 19.03.13
API version: 1.40
Go version: go1.13.15
Git commit: 4484c46d9d
Built: Wed Sep 16 17:03:45 2020
OS/Arch: linux/amd64
Experimental: false
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The location property specified in the multi-container yml deployment file is ignored. The resulting ACI is always deployed in the default location of the resource group.
The text was updated successfully, but these errors were encountered: