Skip to content
This repository has been archived by the owner on Jun 17, 2024. It is now read-only.

location specified in yml is ignored #41

Open
liupeirong opened this issue Nov 4, 2020 · 1 comment
Open

location specified in yml is ignored #41

liupeirong opened this issue Nov 4, 2020 · 1 comment

Comments

@liupeirong
Copy link

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.

@magnus-longva-bouvet
Copy link

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants