AWS ecs - All containers gets killed(STOPPED) if one of them exits or killed

Viewed 1978

Env

  • AWS ecs
  • Docker version 17.03.1-ce, build 7392c3b/17.03.1-ce

Problem

We've 3 docker containers in our app.

  • DB
  • DB-seed (DB migration script runner)
  • app-server

DB and app-server gets started, however once the DB-seed exits(as it should) after running some migration scripts. The rest of the containers die(STOP).

This strange behaviour happens only in AWS ecs and never in my local docker setup.

Moreover, killing any of the containers, stops the other containers in AWS-ECS.

Our docker compose file

version: '2'

services:
  db:
    image: db-image
    hostname: db
    cpu_shares: 50
    mem_limit: 3758096384
    volumes:
     - /data/db:/data/db
    ports:
     - "27017:27017"
  db-seed:
    image:db-seed
    cpu_shares: 10
    mem_limit: 504288000
    links:
    - db
  web:
    image: server-image
    cpu_shares: 50
    mem_limit: 3758096384
    ports:
     - "8080:8080"
    links:
    - db

Is this an issue in AWS ecs or a feature(all or none)?

1 Answers
Related