Skip to content
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.

Docker compose doesn't run in specified AWS region #1374

Closed
JackPriceBurns opened this issue Mar 1, 2021 · 2 comments
Closed

Docker compose doesn't run in specified AWS region #1374

JackPriceBurns opened this issue Mar 1, 2021 · 2 comments
Labels
duplicate This issue or pull request already exists ecs

Comments

@JackPriceBurns
Copy link

Description of the issue

Docker compose does not respect the AWS region you choose when you make a new docker context for ECS.

Context information (for bug reports)

Output of docker-compose version

docker-compose version 1.27.4, build 40524192
docker-py version: 4.3.1
CPython version: 3.7.7
OpenSSL version: OpenSSL 1.1.1g  21 Apr 2020

Output of docker version

Client: Docker Engine - Community
 Cloud integration: 1.0.7
 Version:           20.10.2
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        2291f61
 Built:             Mon Dec 28 16:12:42 2020
 OS/Arch:           darwin/amd64
 Context:           launch-aws
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.2
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       8891c58
  Built:            Mon Dec 28 16:15:28 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.3
  GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b
 runc:
  Version:          1.0.0-rc92
  GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Output of docker-compose config
(Make sure to add the relevant -f and other flags)

services:
  nginx:
    image: nginx
    ports:
    - published: 80
      target: 80
version: '3'

Output of docker context ls

NAME                TYPE                DESCRIPTION                               DOCKER ENDPOINT               KUBERNETES ENDPOINT   ORCHESTRATOR
default             moby                Current DOCKER_HOST based configuration   unix:///var/run/docker.sock                         swarm
---------           ecs-local           ECS local endpoints
---------           ecs                 (eu-west-1)
--------- *         ecs                 (eu-west-1)

I removed the name of my contexts, but it clearly says eu-west-1

Steps to reproduce the issue

  1. Create a new docker context for ECS and specify the region as eu-west-1
  2. Run docker context use {your_newly_created_context}
  3. Run docker compose up

Furthermore if you specify x-aws-cluster and set it to an ECS cluster in eu-west-1 as the documentation says you can do here it doesn't work and gives you the error InvalidParameterException: Invalid Region in ARN which also indicates that it's operating in the wrong region entirely.

Observed result

All of the infrastructure is created within us-east-1

Expected result

For the infrastructure to be created in eu-west-1

@aiordache aiordache transferred this issue from docker/compose Mar 1, 2021
@JackPriceBurns
Copy link
Author

Looks like this issue is related to #1056 #1214 and #1084

@ndeloof ndeloof added ecs duplicate This issue or pull request already exists labels Mar 5, 2021
@ndeloof ndeloof closed this as completed Mar 5, 2021
@JackPriceBurns
Copy link
Author

@ndeloof I'm happy with this issue being closed as it's a duplicate.
However, is there actually being something done about this? The other issues seem to be stagnant and nothing seems to be happening about this issue that has been reported by a few people.

Unfortunately my team have actually decided to stop using docker compose due to these issues and some other limitations.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists ecs
Projects
None yet
Development

No branches or pull requests

2 participants