Running containers on multiple AWS EC2 instances from docker-compose file
up vote
0
down vote
favorite
I know it is not possible to run containers on multiple hosts using a single docker-compose file. And this needs something like docker swarm to do it.
Is there anything equivalent to this on AWS - ECS or Fargate?
docker-compose amazon-ecs
add a comment |
up vote
0
down vote
favorite
I know it is not possible to run containers on multiple hosts using a single docker-compose file. And this needs something like docker swarm to do it.
Is there anything equivalent to this on AWS - ECS or Fargate?
docker-compose amazon-ecs
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I know it is not possible to run containers on multiple hosts using a single docker-compose file. And this needs something like docker swarm to do it.
Is there anything equivalent to this on AWS - ECS or Fargate?
docker-compose amazon-ecs
I know it is not possible to run containers on multiple hosts using a single docker-compose file. And this needs something like docker swarm to do it.
Is there anything equivalent to this on AWS - ECS or Fargate?
docker-compose amazon-ecs
docker-compose amazon-ecs
asked Nov 11 at 5:18
Gautham K
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Yes, You can do this on ECS using EC2 type or using Fargate type cluster.
If you are moving with ECS EC2 Type model you can opt for different task placement strategies for placing your task on different nodes to achieve any model you want like AZ Spread, Binpack etc
Ref: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-strategies.html
If you are opting for Fargate ECS Type then you don't have to take care of underlying EC2 nodes as those are managed by AWS in this case.
Also, there is a big difference in docker-compose and docker-swarm.
Docker swarm is the orchestration which is required for your use case as of now.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Yes, You can do this on ECS using EC2 type or using Fargate type cluster.
If you are moving with ECS EC2 Type model you can opt for different task placement strategies for placing your task on different nodes to achieve any model you want like AZ Spread, Binpack etc
Ref: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-strategies.html
If you are opting for Fargate ECS Type then you don't have to take care of underlying EC2 nodes as those are managed by AWS in this case.
Also, there is a big difference in docker-compose and docker-swarm.
Docker swarm is the orchestration which is required for your use case as of now.
add a comment |
up vote
0
down vote
Yes, You can do this on ECS using EC2 type or using Fargate type cluster.
If you are moving with ECS EC2 Type model you can opt for different task placement strategies for placing your task on different nodes to achieve any model you want like AZ Spread, Binpack etc
Ref: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-strategies.html
If you are opting for Fargate ECS Type then you don't have to take care of underlying EC2 nodes as those are managed by AWS in this case.
Also, there is a big difference in docker-compose and docker-swarm.
Docker swarm is the orchestration which is required for your use case as of now.
add a comment |
up vote
0
down vote
up vote
0
down vote
Yes, You can do this on ECS using EC2 type or using Fargate type cluster.
If you are moving with ECS EC2 Type model you can opt for different task placement strategies for placing your task on different nodes to achieve any model you want like AZ Spread, Binpack etc
Ref: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-strategies.html
If you are opting for Fargate ECS Type then you don't have to take care of underlying EC2 nodes as those are managed by AWS in this case.
Also, there is a big difference in docker-compose and docker-swarm.
Docker swarm is the orchestration which is required for your use case as of now.
Yes, You can do this on ECS using EC2 type or using Fargate type cluster.
If you are moving with ECS EC2 Type model you can opt for different task placement strategies for placing your task on different nodes to achieve any model you want like AZ Spread, Binpack etc
Ref: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement-strategies.html
If you are opting for Fargate ECS Type then you don't have to take care of underlying EC2 nodes as those are managed by AWS in this case.
Also, there is a big difference in docker-compose and docker-swarm.
Docker swarm is the orchestration which is required for your use case as of now.
answered Nov 11 at 5:41
Mohit Kumar
573420
573420
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53246051%2frunning-containers-on-multiple-aws-ec2-instances-from-docker-compose-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown