I'm stuck at writing dockerrun.aws.json for aws ecs

Hi.
I followed along Wiki stuffs like base usage and persistent data parts.
It says make three writable volumes, but i'm not sure about how to write this on dockerrun.aws.json file.
All examples make use of anonymous or nameed volumes for these three volumes.
I don't know how to implement this on dockerrun.aws.json file and i think i make host volumes for all the things.
{
  "AWSEBDockerrunVersion": 2,
  "volumes": [
    {
      "name": "vhost",
      "host": {
        "sourcePath": "/etc/nginx/vhost.d"
      }
    },
    {
      "name": "html",
      "host": {
        "sourcePath": "/usr/share/nginx/html"
      }
    },
    {
      "name": "certs",
      "host": {
        "sourcePath": "/var/app/current/certs"
      }
    },
    {
      "name": "sock",
      "host": {
        "sourcePath": "/var/app/current/sock"
      }
    }
  ],
  "containerDefinitions": [
    {
      "name": "client",
      "image": "west0321/multi-client",
      "hostname": "client",
      "essential": false,
      "memory": 64,
      "environment": [
        {
          "name": "VIRTUAL_HOST",
          "value": "pyochan.com,www.pyochan.com"
        },
        {
          "name": "LETSENCRYPT_HOST",
          "value": "pyochan.com,www.pyochan.com"
        }
      ]
    },
    {
      "name": "server",
      "image": "west0321/multi-server",
      "hostname": "api",
      "essential": false,
      "memory": 64,
      "environment": [
        {
          "name": "VIRTUAL_HOST",
          "value": "api.pyochan.com"
        },
        {
          "name": "LETSENCRYPT_HOST",
          "value": "api.pyochan.com"
        }
      ]
    },
    {
      "name": "worker",
      "image": "west0321/multi-worker",
      "hostname": "worker",
      "essential": false,
      "memory": 64
    },
    {
      "name": "nginx-proxy",
      "image": "jwilder/nginx-proxy",
      "hostname": "nginx-proxy",
      "essential": true,
      "portMappings": [
        {
          "hostPort": 80,
          "containerPort": 80
        },
        {
          "hostPort": 443,
          "containerPort": 443
        }
      ],
      "links": ["client", "server", "letsencrypt"],
      "memory": 64,
      "dockerLabels": {
        "com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy": "true"
      },
      "mountPoints": [
        {
          "sourceVolume": "vhost",
          "containerPath": "/etc/nginx/vhost.d"
        },
        {
          "sourceVolume": "html",
          "containerPath": "/usr/share/nginx/html"
        },
        {
          "sourceVolume": "certs",
          "containerPath": "/etc/nginx/certs"
        },
        {
          "sourceVolume": "sock",
          "containerPath": "/tmp/docker.sock"
        }
      ]
    },
    {
      "name": "letsencrypt",
      "image": "jrcs/letsencrypt-nginx-proxy-companion",
      "hostname": "letsencrypt",
      "essential": false,
      "memory": 64,
      "mountPoints": [
        {
          "sourceVolume": "certs",
          "containerPath": "/etc/nginx/certs"
        },
        {
          "sourceVolume": "sock",
          "containerPath": "/var/run/docker.sock"
        }
      ],
      "volumesFrom": [
        {
          "sourceContainer": "nginx-proxy"
        }
      ]
    }
  ]
}

Could you tell me whether my dockerrun.aws.json file is correct or not.
Would you be able to give an example for dockerrun.aws.json file for this library?
Any help would be really appreciated.
https://github.com/Feelthewind/multi-docker
I got error message like below.
/var/log/ecs/ecs-agent.log.2018-10-12-04
2018-10-12T04:02:04Z [INFO] TCS Websocket connection closed for a valid reason
2018-10-12T04:02:04Z [INFO] Connected to TCS endpoint
2018-10-12T04:06:54Z [INFO] Handling http requestmethodGETfrom<IP_ADDRESS>:54736
2018-10-12T04:07:00Z [WARN] Could not resolve some containers: [[nginx-proxy(jwilder/nginx-proxy) (NONE->RUNNING) letsencrypt(jrcs/letsencrypt-nginx-proxy-companion) (NONE->RUNNING)]] for task awseb-MultiDocker-env-myufbmg9mm:10 arn:aws:ecs:ap-northeast-1:223630899131:task/a5f14f58-6d24-43f8-bce7-f11188e2ce71, TaskStatus: (STOPPED->STOPPED) Containers: [worker (NONE->RUNNING),client (NONE->RUNNING),server (NONE->RUNNING),nginx-proxy (NONE->RUNNING),letsencrypt (NONE->RUNNING),]
2018-10-12T04:07:00Z [ERROR] Task engine [arn:aws:ecs:ap-northeast-1:223630899131:task/a5f14f58-6d24-43f8-bce7-f11188e2ce71]: unable to progress task with circular dependencies

/var/log/eb-activity.log
[2018-10-12T04:55:27.034Z] INFO  [32096] - [Application update travis-3f59e23ce96309a4d80a84edb477232a01f914a2-1539320107@9/AppDeployStage0/EbExtensionPostBuild] : Completed activity.
[2018-10-12T04:55:27.035Z] INFO  [32096] - [Application update travis-3f59e23ce96309a4d80a84edb477232a01f914a2-1539320107@9/AppDeployStage0/InfraCleanEbextension] : Starting activity...
[2018-10-12T04:55:27.037Z] INFO  [32096] - [Application update travis-3f59e23ce96309a4d80a84edb477232a01f914a2-1539320107@9/AppDeployStage0/InfraCleanEbextension] : Completed activity. Result:
Cleaned ebextensions subdirectories from /var/app/staging.
[2018-10-12T04:55:27.037Z] INFO  [32096] - [Application update travis-3f59e23ce96309a4d80a84edb477232a01f914a2-1539320107@9/AppDeployStage0] : Completed activity. Result:
Application update - Command CMD-AppDeploy stage 0 completed
[2018-10-12T04:55:27.037Z] INFO  [32096] - [Application update travis-3f59e23ce96309a4d80a84edb477232a01f914a2-1539320107@9/AppDeployStage1] : Starting activity...
[2018-10-12T04:55:27.037Z] INFO  [32096] - [Application update travis-3f59e23ce96309a4d80a84edb477232a01f914a2-1539320107@9/AppDeployStage1/AppDeployEnactHook] : Starting activity...
[2018-10-12T04:55:27.038Z] INFO  [32096] - [Application update<EMAIL_ADDRESS>: Starting activity...
[2018-10-12T04:55:27.048Z] INFO  [32096] - [Application update<EMAIL_ADDRESS>: Completed activity. Result:

grep -q 'eb-ecs start/'
initctl status eb-ecs
[2018-10-12T04:55:27.048Z] INFO  [32096] - [Application update<EMAIL_ADDRESS>: Starting activity...
[2018-10-12T04:55:27.438Z] INFO  [32096] - [Application update<EMAIL_ADDRESS>: Completed activity. Result:
. /opt/elasticbeanstalk/hooks/common.sh
++ /opt/elasticbeanstalk/bin/get-config container -k app_deploy_dir
EB_CONFIG_APP_CURRENT=/var/app/current
++ /opt/elasticbeanstalk/bin/get-config container -k app_staging_dir
EB_CONFIG_APP_STAGING=/var/app/staging
'[' -z /var/app/staging ']'
'[' -d /var/app/current ']'
mv /var/app/current /var/app/current.old
mv /var/app/staging /var/app/current
nohup rm -rf /var/app/current.old
[2018-10-12T04:55:27.438Z] INFO  [32096] - [Application update<EMAIL_ADDRESS>: Starting activity...
[2018-10-12T04:55:27.870Z] INFO  [32096] - [Application update<EMAIL_ADDRESS>: Completed activity.
[2018-10-12T04:55:27.870Z] INFO  [32096] - [Application update<EMAIL_ADDRESS>: Starting activity...
[2018-10-12T04:56:09.900Z] INFO  [32096] - [Application update<EMAIL_ADDRESS>: Activity execution failed, because: + . /opt/elasticbeanstalk/hooks/common.sh
RETRY=0
initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20181012-32096-tmqpx8
initctl: Job failed to start
'[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
warn 'Failed to start ECS task, retrying...'
echo 'Failed to start ECS task, retrying...'
Failed to start ECS task, retrying...
eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
RETRY=1
sleep 3
'[' 1 -gt 1 ']'
initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20181012-32096-tmqpx8
initctl: Job failed to start
'[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
warn 'Failed to start ECS task, retrying...'
echo 'Failed to start ECS task, retrying...'
Failed to start ECS task, retrying...
eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
RETRY=2
sleep 3
'[' 2 -gt 1 ']'
error_exit 'Failed to start ECS task after retrying 2 times.' 1
error 'Failed to start ECS task after retrying 2 times.'
echo 'Failed to start ECS task after retrying 2 times.'
Failed to start ECS task after retrying 2 times.
eventHelper.py --msg 'Failed to start ECS task after retrying 2 times.' --severity ERROR
exit 1 (ElasticBeanstalk::ExternalInvocationError)
caused by: + . /opt/elasticbeanstalk/hooks/common.sh
RETRY=0
initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20181012-32096-tmqpx8
initctl: Job failed to start
'[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
warn 'Failed to start ECS task, retrying...'
echo 'Failed to start ECS task, retrying...'
Failed to start ECS task, retrying...
eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
RETRY=1
sleep 3
'[' 1 -gt 1 ']'
initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20181012-32096-tmqpx8
initctl: Job failed to start
'[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
warn 'Failed to start ECS task, retrying...'
echo 'Failed to start ECS task, retrying...'
Failed to start ECS task, retrying...
eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
RETRY=2
sleep 3
'[' 2 -gt 1 ']'
error_exit 'Failed to start ECS task after retrying 2 times.' 1
error 'Failed to start ECS task after retrying 2 times.'
echo 'Failed to start ECS task after retrying 2 times.'
Failed to start ECS task after retrying 2 times.
eventHelper.py --msg 'Failed to start ECS task after retrying 2 times.' --severity ERROR

@Feelthewind I'm in the same boat with the same errors and an almost identical config. Will post more as I continue to debug.

Multi-docker Elastic Beanstalk.
My Dockerrun.aws.json
{
  "AWSEBDockerrunVersion": 2,
  "volumes": [
    {
      "name": "nginx-vhostd",
      "host": { "sourcePath": "/etc/nginx/vhost.d" }
    },
    {
      "name": "nginx-html",
      "host": { "sourcePath": "/usr/share/nginx/html" }
    },
    {
      "name": "nginx-certs",
      "host": { "sourcePath": "/home/ec2-user/certs" }
    },
    {
      "name": "docker-sock",
      "host": { "sourcePath": "/var/run/docker.sock" }
    }
  ],
  "containerDefinitions": [
    {
      "name": "nginx",
      "image": "jwilder/nginx-proxy",
      "essential": true,
      "memoryReservation": 128,
      "dockerLabels": {
        "com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy": "true"
      },
      "mountPoints": [
        {
          "containerPath": "/etc/nginx/vhost.d",
          "sourceVolume": "nginx-vhostd"
        },
        {
          "containerPath": "/usr/share/nginx/html",
          "sourceVolume": "nginx-html"
        },
        {
          "containerPath": "/etc/nginx/certs",
          "sourceVolume": "nginx-certs",
          "readOnly": true
        },
        {
          "containerPath": "/tmp/docker.sock",
          "sourceVolume": "docker-sock",
          "readOnly": true
        }
      ],
      "portMappings": [
        { "containerPort": 80, "hostPort": 80 },
        { "containerPort": 443, "hostPort": 443 }
      ]
    },
    {
      "name": "nginx-letsencrypt",
      "image": "jrcs/letsencrypt-nginx-proxy-companion",
      "essential": true,
      "memoryReservation": 64,
      "links": [ "nginx" ],
      "mountPoints": [
        {
          "containerPath": "/etc/nginx/certs",
          "sourceVolume": "nginx-certs"
        },
        {
          "containerPath": "/var/run/docker.sock",
          "sourceVolume": "docker-sock",
          "readOnly": true
        }
      ]
    },
    {
      "name": "traccar",
      "image": "openjdk:8-jre-alpine",
      "memory": 256,
      "portMappings": [
        { "hostPort": 8082, "containerPort": 8082 },
        { "hostPort": 5055, "containerPort": 5055 }
      ],
      "environment": [
        { "name": "VIRTUAL_HOST", "value": "xxx.xxx.com" },
        { "name": "VIRTUAL_PORT", "value": "8082" },
        { "name": "LETSENCRYPT_HOST", "value": "xxx.xxx.com" },
        { "name": "LETSENCRYPT_EMAIL", "value"<EMAIL_ADDRESS>}
      ]
    }
  ]
}

eb deploy error:
2018-10-26 04:36:34    INFO    Environment update is starting.
2018-10-26 04:36:49    INFO    Deploying new version to instance(s).
2018-10-26 04:37:17    ERROR   Failed to start ECS task: arn:aws:ecs:us-west-2:966821920696:task/b8ced724-6a08-420e-8e8c-d533865a8f50 is STOPPED.
2018-10-26 04:37:17    ERROR   ECS task stopped due to: Task failed to start. (nginx-letsencrypt:
nginx:
traccar: )
2018-10-26 04:37:25    ERROR   ECS task stopped due to: Task failed to start. (nginx:
traccar:
nginx-letsencrypt: )
2018-10-26 04:37:25    ERROR   Failed to start ECS task: arn:aws:ecs:us-west-2:966821920696:task/ee88ad37-d611-4f25-8d50-69eda81e6b0e is STOPPED.
2018-10-26 04:37:28    ERROR   Failed to start ECS task after retrying 2 times.
2018-10-26 04:37:30    ERROR   [Instance: i-0d2477023b6eea177] Command failed on instance. Return code: 1 Output: .' --severity ERROR
+ exit 1.
Hook /opt/elasticbeanstalk/hooks/appdeploy/enact/03start-task.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
2018-10-26 04:37:30    INFO    Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2018-10-26 04:37:30    ERROR   Unsuccessful command execution on instance id(s) 'i-0d2477023b6eea177'. Aborting the operation.
2018-10-26 04:37:30    ERROR   Failed to deploy application.

ERROR: ServiceError - Failed to deploy application.
make: *** [deploy] Error 4

tail -100 /var/log/eb-activity.log:
[2018-10-26T04:37:03.600Z] INFO  [20389] - [Application update<EMAIL_ADDRESS>: Starting activity...
[2018-10-26T04:37:03.824Z] INFO  [20389] - [Application update<EMAIL_ADDRESS>: Completed activity.
[2018-10-26T04:37:03.824Z] INFO  [20389] - [Application update<EMAIL_ADDRESS>: Starting activity...
[2018-10-26T04:37:29.007Z] INFO  [20389] - [Application update<EMAIL_ADDRESS>: Activity execution failed, because: + . /opt/elasticbeanstalk/hooks/common.sh
  + RETRY=0
  + initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20181026-20389-13sqqwv
  initctl: Job failed to start
  + '[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
  + warn 'Failed to start ECS task, retrying...'
  + echo 'Failed to start ECS task, retrying...'
  Failed to start ECS task, retrying...
  + eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
  + RETRY=1
  + sleep 3
  + '[' 1 -gt 1 ']'
  + initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20181026-20389-13sqqwv
  initctl: Job failed to start
  + '[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
  + warn 'Failed to start ECS task, retrying...'
  + echo 'Failed to start ECS task, retrying...'
  Failed to start ECS task, retrying...
  + eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
  + RETRY=2
  + sleep 3
  + '[' 2 -gt 1 ']'
  + error_exit 'Failed to start ECS task after retrying 2 times.' 1
  + error 'Failed to start ECS task after retrying 2 times.'
  + echo 'Failed to start ECS task after retrying 2 times.'
  Failed to start ECS task after retrying 2 times.
  + eventHelper.py --msg 'Failed to start ECS task after retrying 2 times.' --severity ERROR
  + exit 1 (ElasticBeanstalk::ExternalInvocationError)
caused by: + . /opt/elasticbeanstalk/hooks/common.sh
  + RETRY=0
  + initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20181026-20389-13sqqwv
  initctl: Job failed to start
  + '[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
  + warn 'Failed to start ECS task, retrying...'
  + echo 'Failed to start ECS task, retrying...'
  Failed to start ECS task, retrying...
  + eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
  + RETRY=1
  + sleep 3
  + '[' 1 -gt 1 ']'
  + initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20181026-20389-13sqqwv
  initctl: Job failed to start
  + '[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
  + warn 'Failed to start ECS task, retrying...'
  + echo 'Failed to start ECS task, retrying...'
  Failed to start ECS task, retrying...
  + eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
  + RETRY=2
  + sleep 3
  + '[' 2 -gt 1 ']'
  + error_exit 'Failed to start ECS task after retrying 2 times.' 1
  + error 'Failed to start ECS task after retrying 2 times.'
  + echo 'Failed to start ECS task after retrying 2 times.'
  Failed to start ECS task after retrying 2 times.
  + eventHelper.py --msg 'Failed to start ECS task after retrying 2 times.' --severity ERROR
  + exit 1 (Executor::NonZeroExitStatus)

[2018-10-26T04:37:29.008Z] INFO  [20389] - [Application update<EMAIL_ADDRESS>: Activity failed.
[2018-10-26T04:37:29.008Z] INFO  [20389] - [Application update app-ecdd-181025_213432-stage-181025_213432@14/AppDeployStage1/AppDeployEnactHook] : Activity failed.
[2018-10-26T04:37:29.008Z] INFO  [20389] - [Application update app-ecdd-181025_213432-stage-181025_213432@14/AppDeployStage1] : Activity fa
iled.
[2018-10-26T04:37:29.008Z] INFO  [20389] - [Application update app-ecdd-181025_213432-stage-181025_213432@14] : Completed activity. Result:
  Application update - Command CMD-AppDeploy failed

docker logs:
WARNING: /etc/nginx/dhparam/dhparam.pem was not found. A pre-generated dhparam.pem will be used for now while a new one
is being generated in the background.  Once the new dhparam.pem is in place, nginx will be reloaded.
forego     | starting dockergen.1 on port 5000
forego     | starting nginx.1 on port 5100
dockergen.1 | 2018/10/26 04:37:24 Generated '/etc/nginx/conf.d/default.conf' from 3 containers
dockergen.1 | 2018/10/26 04:37:24 Running 'nginx -s reload'
dockergen.1 | 2018/10/26 04:37:24 Error running notify command: nginx -s reload, exit status 1
dockergen.1 | 2018/10/26 04:37:24 Watching docker events

If any of you managed to solve the issue, can you please write how?

Any progress on this?

@thecritic no progress. As mentioned above this is blocked by a nginx-proxy / docker-gen bug specific to AWS ECS.

Is there any progress on this issue? I'm having the same issue while trying to deploy nginx letsencrypt-companion and my web app onto elastic beanstalk.

Here's my docker config and log info:
dockerrun.aws.json:
{
  "AWSEBDockerrunVersion": "2",
  "volumes": [
    {
      "name": "vhost",
      "sourcePath": "/etc/nginx/vhost.d"
    },
    {
      "name": "html",
      "sourcePath": "/usr/share/nginx/html"
    },
    {
      "name": "certs",
      "sourcePath": "/var/app/current/certs"
    },
    {
      "name": "sock",
      "host":{
        "sourcePath": "/var/run/docker.sock"
      }
    }
  ],
  "containerDefinitions": [
    {
      "name": "nginx-proxy",
      "image": "jwilder/nginx-proxy",
      "essential": true,
      "memory": 128,
      "portMappings": [
        {
          "hostPort": 80,
          "containerPort": 80
        },
        {
          "hostPort": 443,
          "containerPort": 443
        }
      ],
      "links": [
        "web-app"
      ],
      "mountPoints": [
        {
          "sourceVolume": "vhost",
          "containerPath": "/etc/nginx/vhost.d"
        },
        {
          "sourceVolume": "certs",
          "containerPath": "/etc/nginx/certs",
          "readOnly": true
        },
        {
          "sourceVolume": "sock",
          "containerPath": "/tmp/docker.sock",
          "readOnly": true
        },
        {
          "sourceVolume": "awseb-logs-nginx-proxy",
          "containerPath": "/var/log/nginx"
        },
        {
          "sourceVolume": "html",
          "containerPath":"/usr/share/nginx/html"
        }
      ]
    },
    {
      "name": "nginx-proxy-le",
      "image": "jrcs/letsencrypt-nginx-proxy-companion",
      "essential": true,
      "memory": 128,
      "volumesFrom": [
        {
          "sourceContainer": "nginx-proxy"
        }
      ],
      "mountPoints": [
        {
          "sourceVolume": "certs",
          "containerPath": "/etc/nginx/certs"
        },
        {
          "sourceVolume": "sock",
          "containerPath": "/var/run/docker.sock",
          "readOnly": true
        }
      ]
    },
    {
      "name": "web-app",
      "image": "hugozzys/webapp:latest",
      "essential": true,
      "portMappings": [
        {
          "hostPort": 8080,
          "containerPort": 8080
        }
      ],
      "memory": 128,
      "environment": [
        {
          "name": "VIRTUAL_HOST",
          "value":"random.hugozh.com"
        },
        {
          "name": "LETSENCRYPT_HOST",
          "value":"random.hugozh.com"
        },
        {
          "name": "LETSENCRYPT_EMAIL",
<EMAIL_ADDRESS>        },
        {
          "name": "VIRTUAL_PORT",
          "value": "8080"
        }
      ]
    }
  ]
}

eb-activitiy.log:
 ++ jq -r '.containerDefinitions[].name'
  ++ cat /var/app/staging/Dockerrun.aws.json
  + for CONTAINER in '`cat $EB_CONFIG_APP_STAGING/Dockerrun.aws.json | jq -r .containerDefinitions[].name`'
  + CONTAINER_LOG_DIR=/var/log/containers/nginx-proxy
  + mkdir -p /var/log/containers/nginx-proxy
  + chmod 777 /var/log/containers/nginx-proxy
  + /opt/elasticbeanstalk/bin/log-conf -n applogs-nginx-proxy '-l/var/log/containers/nginx-proxy/*.log' -r size=1M,rotate=5
  + /opt/elasticbeanstalk/bin/log-conf -n applogs-nginx-proxy-rotated '-l/var/log/containers/nginx-proxy.log*' -t bundlelogs
  + for CONTAINER in '`cat $EB_CONFIG_APP_STAGING/Dockerrun.aws.json | jq -r .containerDefinitions[].name`'
  + CONTAINER_LOG_DIR=/var/log/containers/nginx-proxy-le
  + mkdir -p /var/log/containers/nginx-proxy-le
  + chmod 777 /var/log/containers/nginx-proxy-le
  + /opt/elasticbeanstalk/bin/log-conf -n applogs-nginx-proxy-le '-l/var/log/containers/nginx-proxy-le/*.log' -r size=1M,rotate=5
  + /opt/elasticbeanstalk/bin/log-conf -n applogs-nginx-proxy-le-rotated '-l/var/log/containers/nginx-proxy-le.log*' -t bundlelogs
  + for CONTAINER in '`cat $EB_CONFIG_APP_STAGING/Dockerrun.aws.json | jq -r .containerDefinitions[].name`'
  + CONTAINER_LOG_DIR=/var/log/containers/web-app
  + mkdir -p /var/log/containers/web-app
  + chmod 777 /var/log/containers/web-app
  + /opt/elasticbeanstalk/bin/log-conf -n applogs-web-app '-l/var/log/containers/web-app/*.log' -r size=1M,rotate=5
  + /opt/elasticbeanstalk/bin/log-conf -n applogs-web-app-rotated '-l/var/log/containers/web-app.log*' -t bundlelogs
[2019-09-14T21:29:01.887Z] INFO  [1755]  - [Application update<EMAIL_ADDRESS>: Starting activity...
[2019-09-14T21:29:01.975Z] INFO  [1755]  - [Application update<EMAIL_ADDRESS>: Completed activity.
[2019-09-14T21:29:01.975Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage0/AppDeployPreHook] : Completed activity. Result:
  Successfully execute hooks in directory /opt/elasticbeanstalk/hooks/appdeploy/pre.
[2019-09-14T21:29:01.975Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage0/EbExtensionPostBuild] : Starting activity...
[2019-09-14T21:29:02.334Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage0/EbExtensionPostBuild/Infra-EmbeddedPostBuild] : Starting activity...
[2019-09-14T21:29:02.334Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage0/EbExtensionPostBuild/Infra-EmbeddedPostBuild] : Completed activity.
[2019-09-14T21:29:02.352Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage0/EbExtensionPostBuild] : Completed activity.
[2019-09-14T21:29:02.352Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage0/InfraCleanEbextension] : Starting activity...
[2019-09-14T21:29:02.353Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage0/InfraCleanEbextension] : Completed activity. Result:
  Cleaned ebextensions subdirectories from /var/app/staging.
[2019-09-14T21:29:02.353Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage0] : Completed activity. Result:
  Application update - Command CMD-AppDeploy stage 0 completed
[2019-09-14T21:29:02.353Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage1] : Starting activity...
[2019-09-14T21:29:02.353Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage1/AppDeployEnactHook] : Starting activity...
[2019-09-14T21:29:02.353Z] INFO  [1755]  - [Application update<EMAIL_ADDRESS>: Starting activity...
[2019-09-14T21:29:02.359Z] INFO  [1755]  - [Application update<EMAIL_ADDRESS>: Completed activity. Result:
  + grep -q 'eb-ecs start/'
  + initctl status eb-ecs
[2019-09-14T21:29:02.359Z] INFO  [1755]  - [Application update<EMAIL_ADDRESS>: Starting activity...
[2019-09-14T21:29:02.555Z] INFO  [1755]  - [Application update<EMAIL_ADDRESS>: Completed activity. Result:
  + . /opt/elasticbeanstalk/hooks/common.sh
  ++ /opt/elasticbeanstalk/bin/get-config container -k app_deploy_dir
  + EB_CONFIG_APP_CURRENT=/var/app/current
  ++ /opt/elasticbeanstalk/bin/get-config container -k app_staging_dir
  + EB_CONFIG_APP_STAGING=/var/app/staging
  + '[' -z /var/app/staging ']'
  + '[' -d /var/app/current ']'
  + mv /var/app/current /var/app/current.old
  + mv /var/app/staging /var/app/current
  + nohup rm -rf /var/app/current.old
[2019-09-14T21:29:02.555Z] INFO  [1755]  - [Application update<EMAIL_ADDRESS>: Starting activity...
[2019-09-14T21:29:02.767Z] INFO  [1755]  - [Application update<EMAIL_ADDRESS>: Completed activity.
[2019-09-14T21:29:02.767Z] INFO  [1755]  - [Application update<EMAIL_ADDRESS>: Starting activity...
[2019-09-14T21:29:37.769Z] INFO  [1755]  - [Application update<EMAIL_ADDRESS>: Activity execution failed, because: + . /opt/elasticbeanstalk/hooks/common.sh
  + RETRY=0
  + initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20190914-1755-1lvc6em
  initctl: Job failed to start
  + '[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
  + warn 'Failed to start ECS task, retrying...'
  + echo 'Failed to start ECS task, retrying...'
  Failed to start ECS task, retrying...
  + eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
  + RETRY=1
  + sleep 3
  + '[' 1 -gt 1 ']'
  + initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20190914-1755-1lvc6em
  initctl: Job failed to start
  + '[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
  + warn 'Failed to start ECS task, retrying...'
  + echo 'Failed to start ECS task, retrying...'
  Failed to start ECS task, retrying...
  + eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
  + RETRY=2
  + sleep 3
  + '[' 2 -gt 1 ']'
  + error_exit 'Failed to start ECS task after retrying 2 times.' 1
  + error 'Failed to start ECS task after retrying 2 times.'
  + echo 'Failed to start ECS task after retrying 2 times.'
  Failed to start ECS task after retrying 2 times.
  + eventHelper.py --msg 'Failed to start ECS task after retrying 2 times.' --severity ERROR
  + exit 1 (ElasticBeanstalk::ExternalInvocationError)
caused by: + . /opt/elasticbeanstalk/hooks/common.sh
  + RETRY=0
  + initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20190914-1755-1lvc6em
  initctl: Job failed to start
  + '[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
  + warn 'Failed to start ECS task, retrying...'
  + echo 'Failed to start ECS task, retrying...'
  Failed to start ECS task, retrying...
  + eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
  + RETRY=1
  + sleep 3
  + '[' 1 -gt 1 ']'
  + initctl start eb-ecs EB_EVENT_FILE=/tmp/eventsfile20190914-1755-1lvc6em
  initctl: Job failed to start
  + '[' -f /etc/elasticbeanstalk/.eb-ecs-start-no-retry ']'
  + warn 'Failed to start ECS task, retrying...'
  + echo 'Failed to start ECS task, retrying...'
  Failed to start ECS task, retrying...
  + eventHelper.py --msg 'Failed to start ECS task, retrying...' --severity WARN
  + RETRY=2
  + sleep 3
  + '[' 2 -gt 1 ']'
  + error_exit 'Failed to start ECS task after retrying 2 times.' 1
  + error 'Failed to start ECS task after retrying 2 times.'
  + echo 'Failed to start ECS task after retrying 2 times.'
  Failed to start ECS task after retrying 2 times.
  + eventHelper.py --msg 'Failed to start ECS task after retrying 2 times.' --severity ERROR
  + exit 1 (Executor::NonZeroExitStatus)

[2019-09-14T21:29:37.770Z] INFO  [1755]  - [Application update<EMAIL_ADDRESS>: Activity failed.
[2019-09-14T21:29:37.770Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage1/AppDeployEnactHook] : Activity failed.
[2019-09-14T21:29:37.770Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11/AppDeployStage1] : Activity failed.
[2019-09-14T21:29:37.770Z] INFO  [1755]  - [Application update jenkins-blogAdminStagingCD-15@11] : Completed activity. Result:
  Application update - Command CMD-AppDeploy failed
[2019-09-14T21:30:08.475Z] INFO  [3567]  - [CMD-BundleLogs] : Starting activity...
[2019-09-14T21:30:08.476Z] INFO  [3567]  - [CMD-BundleLogs/AddonsBefore] : Starting activity...
[2019-09-14T21:30:08.476Z] INFO  [3567]  - [CMD-BundleLogs/AddonsBefore] : Completed activity.
[2019-09-14T21:30:08.476Z] INFO  [3567]  - [CMD-BundleLogs/BundleLogs] : Starting activity...
[2019-09-14T21:30:08.476Z] INFO  [3567]  - [CMD-BundleLogs/BundleLogs/BundleLogs] : Starting activity...

ecs-agent:
2019-09-14T21:29:15Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got container [web-app] event: [RUNNING]
2019-09-14T21:29:15Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: handling container change [{RUNNING {e25b994e156e150ac96605b56cfe736b877be85ad023a57cc5091822752ccfe5 <nil> [{8080 8080 <IP_ADDRESS> 0}] <nil> [] map[com.amazonaws.ecs.cluster:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.container-name:web-app com.amazonaws.ecs.task-arn:arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 com.amazonaws.ecs.task-definition-family:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.task-definition-version:14] 2019-09-14 21:29:14.945026948 +0000 UTC 2019-09-14 21:29:15.416513151 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 } default 0xc00018c100} ContainerStatusChangeEvent}] for container [web-app]
2019-09-14T21:29:15Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: redundant container state change. web-app to RUNNING, but already RUNNING
2019-09-14T21:29:15Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: task not steady state or terminal; progressing it
2019-09-14T21:29:15Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got container [web-app] event: [STOPPED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: handling container change [{STOPPED {e25b994e156e150ac96605b56cfe736b877be85ad023a57cc5091822752ccfe5 0xc000073700 [] <nil> [] map[com.amazonaws.ecs.cluster:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.container-name:web-app com.amazonaws.ecs.task-arn:arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 com.amazonaws.ecs.task-definition-family:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.task-definition-version:14] 2019-09-14 21:29:14.945026948 +0000 UTC 2019-09-14 21:29:15.416513151 +0000 UTC 2019-09-14 21:29:16.521714743 +0000 UTC {UNKNOWN <nil> 0 } default 0xc00018cb00} ContainerStatusChangeEvent}] for container [web-app]
2019-09-14T21:29:16Z [INFO] Task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: recording execution stopped time. Essential container [web-app] stopped at: 2019-09-14 21:29:16.734006898 +0000 UTC m=+10217.467542074
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: sending container change event [web-app]: arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 web-app -> STOPPED, Exit 139, , Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: sent container change event [web-app]: arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 web-app -> STOPPED, Exit 139, , Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [web-app]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (NONE->RUNNING) Containers: [nginx-proxy (NONE->RUNNING),nginx-proxy-le (NONE->RUNNING),web-app (STOPPED->RUNNING),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (NONE->STOPPED),nginx-proxy-le (NONE->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy-le]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (NONE->STOPPED),nginx-proxy-le (NONE->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [web-app]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (NONE->STOPPED),nginx-proxy-le (NONE->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: task not steady state or terminal; progressing it
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got container [nginx-proxy-le] event: [STOPPED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: handling container change [{STOPPED { <nil> [] <nil> [] map[] 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 }  <nil>} ContainerStatusChangeEvent}] for container [nginx-proxy-le]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: sending container change event [nginx-proxy-le]: arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 nginx-proxy-le -> STOPPED, Known Sent: NONE
2019-09-14T21:29:16Z [INFO] TaskHandler: batching container event: arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 web-app -> STOPPED, Exit 139, , Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:16Z [INFO] TaskHandler: batching container event: arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 nginx-proxy-le -> STOPPED, Known Sent: NONE
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: sent container change event [nginx-proxy-le]: arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 nginx-proxy-le -> STOPPED, Known Sent: NONE
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (NONE->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy-le]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (NONE->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [web-app]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (NONE->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (NONE->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy-le]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (NONE->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [web-app]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (NONE->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: task not steady state or terminal; progressing it
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got container [nginx-proxy] event: [STOPPED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: handling container change [{STOPPED { <nil> [] <nil> [] map[] 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 }  <nil>} ContainerStatusChangeEvent}] for container [nginx-proxy]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: sending container change event [nginx-proxy]: arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 nginx-proxy -> STOPPED, Known Sent: NONE
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: sent container change event [nginx-proxy]: arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 nginx-proxy -> STOPPED, Known Sent: NONE
2019-09-14T21:29:16Z [INFO] api/task: Updating task's known status to: STOPPED, task: awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (STOPPED->STOPPED) Containers: [nginx-proxy (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy-le]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (STOPPED->STOPPED) Containers: [nginx-proxy (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [web-app]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (STOPPED->STOPPED) Containers: [nginx-proxy (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: container change also resulted in task change [nginx-proxy]: [STOPPED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: sending task change event [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 -> STOPPED, Known Sent: NONE, PullStartedAt: 2019-09-14 21:29:04.833164395 +0000 UTC m=+10205.566699569, PullStoppedAt: 2019-09-14 21:29:14.935382278 +0000 UTC m=+10215.668918404, ExecutionStoppedAt: 2019-09-14 21:29:16.734006898 +0000 UTC m=+10217.467542074]
2019-09-14T21:29:16Z [INFO] TaskHandler: batching container event: arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 nginx-proxy -> STOPPED, Known Sent: NONE
2019-09-14T21:29:16Z [INFO] TaskHandler: Adding event: TaskChange: [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 -> STOPPED, Known Sent: NONE, PullStartedAt: 2019-09-14 21:29:04.833164395 +0000 UTC m=+10205.566699569, PullStoppedAt: 2019-09-14 21:29:14.935382278 +0000 UTC m=+10215.668918404, ExecutionStoppedAt: 2019-09-14 21:29:16.734006898 +0000 UTC m=+10217.467542074, arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 web-app -> RUNNING, Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE, arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 web-app -> STOPPED, Exit 139, , Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE, arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 nginx-proxy-le -> STOPPED, Known Sent: NONE, arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 nginx-proxy -> STOPPED, Known Sent: NONE] sent: false
2019-09-14T21:29:16Z [INFO] TaskHandler: Sending task change: TaskChange: [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 -> STOPPED, Known Sent: NONE, PullStartedAt: 2019-09-14 21:29:04.833164395 +0000 UTC m=+10205.566699569, PullStoppedAt: 2019-09-14 21:29:14.935382278 +0000 UTC m=+10215.668918404, ExecutionStoppedAt: 2019-09-14 21:29:16.734006898 +0000 UTC m=+10217.467542074, arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 web-app -> RUNNING, Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE, arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 web-app -> STOPPED, Exit 139, , Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE, arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 nginx-proxy-le -> STOPPED, Known Sent: NONE, arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 nginx-proxy -> STOPPED, Known Sent: NONE] sent: false
2019-09-14T21:29:16Z [WARN] DockerGoClient: Unable to decode stats for container e25b994e156e150ac96605b56cfe736b877be85ad023a57cc5091822752ccfe5: context canceled
2019-09-14T21:29:16Z [INFO] Container e25b994e156e150ac96605b56cfe736b877be85ad023a57cc5091822752ccfe5 is terminal, stopping stats collection
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: sent task change event [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896 -> STOPPED, Known Sent: NONE, PullStartedAt: 2019-09-14 21:29:04.833164395 +0000 UTC m=+10205.566699569, PullStoppedAt: 2019-09-14 21:29:14.935382278 +0000 UTC m=+10215.668918404, ExecutionStoppedAt: 2019-09-14 21:29:16.734006898 +0000 UTC m=+10217.467542074]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (STOPPED->STOPPED) Containers: [nginx-proxy (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy-le]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (STOPPED->STOPPED) Containers: [nginx-proxy (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] api/task: Updating task desired status to stopped because of container: [web-app]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, TaskStatus: (STOPPED->STOPPED) Containers: [nginx-proxy (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),web-app (STOPPED->STOPPED),]]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: task has reached stopped. Waiting for container cleanup
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got resource [cgroup] event: [REMOVED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got resource [vhost] event: [REMOVED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got resource [certs] event: [REMOVED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got resource [html] event: [REMOVED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got resource [certs] event: [REMOVED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got resource [cgroup] event: [REMOVED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: redundant resource state change. cgroup to REMOVED, but already REMOVED
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got resource [vhost] event: [REMOVED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: redundant resource state change. vhost to REMOVED, but already REMOVED
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got resource [certs] event: [REMOVED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: redundant resource state change. certs to REMOVED, but already REMOVED
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got resource [html] event: [REMOVED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: redundant resource state change. html to REMOVED, but already REMOVED
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got resource [certs] event: [REMOVED]
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: redundant resource state change. certs to REMOVED, but already REMOVED
2019-09-14T21:29:16Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:24Z [INFO] Saving state! module="statemanager"
2019-09-14T21:29:26Z [INFO] Adding image name- jwilder/nginx-proxy to Image state- sha256:70d076090cb5edee0408c3f7251dbf43b5e95b6479cd90d334eb53ba01cd0a3e
2019-09-14T21:29:26Z [INFO] Updating container reference nginx-proxy in Image State - sha256:70d076090cb5edee0408c3f7251dbf43b5e95b6479cd90d334eb53ba01cd0a3e
2019-09-14T21:29:26Z [INFO] Saving state! module="statemanager"
2019-09-14T21:29:26Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: finished pulling image jwilder/nginx-proxy for container nginx-proxy in 11.146812322s
2019-09-14T21:29:26Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: got container [nginx-proxy] event: [PULLED]
2019-09-14T21:29:26Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: handling container change [{PULLED { <nil> [] <nil> [] map[] 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 }  <nil>} ContainerStatusChangeEvent}] for container [nginx-proxy]
2019-09-14T21:29:26Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: redundant container state change. nginx-proxy to PULLED, but already STOPPED
2019-09-14T21:29:26Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896]: waiting for event for task
2019-09-14T21:29:26Z [WARN] Could not find requested resource: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: unable to create state change event for container [nginx-proxy]: create container state change event api: status not recognized by ECS: NONE
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: unable to create state change event for container [web-app]: create container state change event api: status not recognized by ECS: NONE
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: unable to create state change event for container [nginx-proxy-le]: create container state change event api: status not recognized by ECS: NONE
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: unable to create task state change event []: create task state change event api: status not recognized by ECS: NONE
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for any previous stops to complete. Sequence number: 15
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: no longer waiting
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: wait over; ready to move towards status: RUNNING
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:27Z [INFO] Creating cgroup /ecs/e8232943-105b-40e8-a421-710abea4e073
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: transitioned resource [cgroup] to [CREATED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got resource [cgroup] event: [CREATED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:27Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: pulling image hugozzys/webapp:latest for container web-app concurrently
2019-09-14T21:29:27Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: recording timestamp for starting image pulltime: 2019-09-14 21:29:27.288763511 +0000 UTC m=+10228.022298674
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: transitioned resource [certs] to [CREATED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got resource [certs] event: [CREATED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: transitioned resource [certs] to [CREATED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got resource [certs] event: [CREATED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: transitioned resource [vhost] to [CREATED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got resource [vhost] event: [CREATED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: transitioned resource [html] to [CREATED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got resource [html] event: [CREATED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:27Z [INFO] Updating container reference web-app in Image State - sha256:5123ebc70d047a8e5df4560e45ca6d2dc88adaf0574269949e622849fbcaeb2e
2019-09-14T21:29:27Z [INFO] Saving state! module="statemanager"
2019-09-14T21:29:27Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: finished pulling image hugozzys/webapp:latest for container web-app in 251.352054ms
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got container [web-app] event: [PULLED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: handling container change [{PULLED { <nil> [] <nil> [] map[] 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 }  <nil>} ContainerStatusChangeEvent}] for container [web-app]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: unable to create state change event for container [web-app]: create container state change event api: status not recognized by ECS: PULLED
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:27Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: creating container: web-app
2019-09-14T21:29:27Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: created container name mapping for task:  web-app -> ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-web-app-a485accf9acee59c7c00
2019-09-14T21:29:27Z [INFO] Saving state! module="statemanager"
2019-09-14T21:29:27Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: created docker container for task: web-app -> 122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618
2019-09-14T21:29:27Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: created docker container for task: web-app -> 122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618, took 150.087089ms
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got container [web-app] event: [CREATED]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: handling container change [{CREATED {122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618 <nil> [] <nil> [] map[com.amazonaws.ecs.cluster:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.container-name:web-app com.amazonaws.ecs.task-arn:arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 com.amazonaws.ecs.task-definition-family:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.task-definition-version:14] 2019-09-14 21:29:27.551480156 +0000 UTC 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 } default 0xc00018ca00} ContainerStatusChangeEvent}] for container [web-app]
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: unable to create state change event for container [web-app]: create container state change event api: status not recognized by ECS: CREATED
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:27Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:27Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: starting container: web-app
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got container [web-app] event: [RUNNING]
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: handling container change [{RUNNING {122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618 <nil> [{8080 8080 <IP_ADDRESS> 0}] <nil> [] map[com.amazonaws.ecs.cluster:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.container-name:web-app com.amazonaws.ecs.task-arn:arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 com.amazonaws.ecs.task-definition-family:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.task-definition-version:14] 2019-09-14 21:29:27.551480156 +0000 UTC 2019-09-14 21:29:28.049357516 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 } default 0xc00018d600} ContainerStatusChangeEvent}] for container [web-app]
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: sending container change event [web-app]: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 web-app -> RUNNING, Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: sent container change event [web-app]: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 web-app -> RUNNING, Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:28Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: pulling image jwilder/nginx-proxy for container nginx-proxy concurrently
2019-09-14T21:29:28Z [INFO] TaskHandler: batching container event: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 web-app -> RUNNING, Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:28Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: started docker container for task: web-app -> 122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618, took 358.876309ms
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got container [web-app] event: [RUNNING]
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: handling container change [{RUNNING {122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618 <nil> [{8080 8080 <IP_ADDRESS> 0}] <nil> [] map[com.amazonaws.ecs.cluster:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.container-name:web-app com.amazonaws.ecs.task-arn:arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 com.amazonaws.ecs.task-definition-family:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.task-definition-version:14] 2019-09-14 21:29:27.551480156 +0000 UTC 2019-09-14 21:29:28.049357516 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 } default 0xc00018de00} ContainerStatusChangeEvent}] for container [web-app]
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: redundant container state change. web-app to RUNNING, but already RUNNING
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:28Z [INFO] Updating container reference nginx-proxy in Image State - sha256:70d076090cb5edee0408c3f7251dbf43b5e95b6479cd90d334eb53ba01cd0a3e
2019-09-14T21:29:28Z [INFO] Saving state! module="statemanager"
2019-09-14T21:29:28Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: finished pulling image jwilder/nginx-proxy for container nginx-proxy in 231.402367ms
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got container [nginx-proxy] event: [PULLED]
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: handling container change [{PULLED { <nil> [] <nil> [] map[] 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 }  <nil>} ContainerStatusChangeEvent}] for container [nginx-proxy]
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: unable to create state change event for container [nginx-proxy]: create container state change event api: status not recognized by ECS: PULLED
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:28Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: creating container: nginx-proxy
2019-09-14T21:29:28Z [WARN] Link name [web-app] found with no linkalias for container: [nginx-proxy(jwilder/nginx-proxy) (PULLED->RUNNING)] in task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, TaskStatus: (NONE->RUNNING) Containers: [nginx-proxy (PULLED->RUNNING),web-app (RUNNING->RUNNING),nginx-proxy-le (NONE->RUNNING),]]
2019-09-14T21:29:28Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: created container name mapping for task:  nginx-proxy -> ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-nginx-proxy-e6e7d78eb8f2879fff01
2019-09-14T21:29:28Z [INFO] Saving state! module="statemanager"
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:28Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: created docker container for task: nginx-proxy -> 83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61
2019-09-14T21:29:28Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: created docker container for task: nginx-proxy -> 83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, took 231.410651ms
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got container [nginx-proxy] event: [CREATED]
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: handling container change [{CREATED {83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61 <nil> [] <nil> [] map[com.amazonaws.ecs.cluster:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.container-name:nginx-proxy com.amazonaws.ecs.task-arn:arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 com.amazonaws.ecs.task-definition-family:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.task-definition-version:14 maintainer:Jason Wilder<EMAIL_ADDRESS>2019-09-14 21:29:28.306193766 +0000 UTC 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 } default 0xc00018ca00} ContainerStatusChangeEvent}] for container [nginx-proxy]
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: unable to create state change event for container [nginx-proxy]: create container state change event api: status not recognized by ECS: CREATED
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:28Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:28Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: pulling image jrcs/letsencrypt-nginx-proxy-companion for container nginx-proxy-le concurrently
2019-09-14T21:29:28Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: starting container: nginx-proxy
2019-09-14T21:29:29Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got container [nginx-proxy] event: [RUNNING]
2019-09-14T21:29:29Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: handling container change [{RUNNING {83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61 <nil> [{443 443 <IP_ADDRESS> 0} {80 80 <IP_ADDRESS> 0}] <nil> [{volume ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-html-e0cde1d1e2afd6c56b00 /var/lib/docker/volumes/ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-html-e0cde1d1e2afd6c56b00/_data /usr/share/nginx/html local z true } {volume 098cbb8e8fcb746fd44eb7c30c7a4c8df631e63358535426250cd922fe906009 /var/lib/docker/volumes/098cbb8e8fcb746fd44eb7c30c7a4c8df631e63358535426250cd922fe906009/_data /etc/nginx/dhparam local  true } {volume ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-vhost-dad59c9bc4b8a4a04900 /var/lib/docker/volumes/ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-vhost-dad59c9bc4b8a4a04900/_data /etc/nginx/vhost.d local z true } {volume ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-certs-9ce9819dc988eedb5600 /var/lib/docker/volumes/ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-certs-9ce9819dc988eedb5600/_data /etc/nginx/certs local ro false } {bind  /var/run/docker.sock /tmp/docker.sock  ro false rprivate} {bind  /var/log/containers/nginx-proxy /var/log/nginx   true rprivate}] map[com.amazonaws.ecs.cluster:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.container-name:nginx-proxy com.amazonaws.ecs.task-arn:arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 com.amazonaws.ecs.task-definition-family:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.task-definition-version:14 maintainer:Jason Wilder<EMAIL_ADDRESS>2019-09-14 21:29:28.306193766 +0000 UTC 2019-09-14 21:29:29.202425293 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 } default 0xc00018d900} ContainerStatusChangeEvent}] for container [nginx-proxy]
2019-09-14T21:29:29Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: sending container change event [nginx-proxy]: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 nginx-proxy -> RUNNING, Ports [{443 443 <IP_ADDRESS> 0} {80 80 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:29Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: sent container change event [nginx-proxy]: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 nginx-proxy -> RUNNING, Ports [{443 443 <IP_ADDRESS> 0} {80 80 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:29Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:29Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:29Z [INFO] TaskHandler: batching container event: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 nginx-proxy -> RUNNING, Ports [{443 443 <IP_ADDRESS> 0} {80 80 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:29Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: started docker container for task: nginx-proxy -> 83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, took 677.065664ms
2019-09-14T21:29:29Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got container [nginx-proxy] event: [RUNNING]
2019-09-14T21:29:29Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: handling container change [{RUNNING {83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61 <nil> [{443 443 <IP_ADDRESS> 0} {80 80 <IP_ADDRESS> 0}] <nil> [] map[com.amazonaws.ecs.cluster:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.container-name:nginx-proxy com.amazonaws.ecs.task-arn:arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 com.amazonaws.ecs.task-definition-family:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.task-definition-version:14 maintainer:Jason Wilder<EMAIL_ADDRESS>2019-09-14 21:29:28.306193766 +0000 UTC 2019-09-14 21:29:29.202425293 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 } default 0xc00058a000} ContainerStatusChangeEvent}] for container [nginx-proxy]
2019-09-14T21:29:29Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: redundant container state change. nginx-proxy to RUNNING, but already RUNNING
2019-09-14T21:29:29Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:29Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:30Z [WARN] Error converting stats for container 122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618: Invalid container statistics reported, no cpu core usage reported
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got container [web-app] event: [STOPPED]
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: handling container change [{STOPPED {122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618 0xc000731e80 [] <nil> [] map[com.amazonaws.ecs.cluster:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.container-name:web-app com.amazonaws.ecs.task-arn:arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 com.amazonaws.ecs.task-definition-family:awseb-BlogAdminStaging-env-1-wvae7y5qub com.amazonaws.ecs.task-definition-version:14] 2019-09-14 21:29:27.551480156 +0000 UTC 2019-09-14 21:29:28.049357516 +0000 UTC 2019-09-14 21:29:30.271958693 +0000 UTC {UNKNOWN <nil> 0 } default 0xc00058ab00} ContainerStatusChangeEvent}] for container [web-app]
2019-09-14T21:29:30Z [INFO] Task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: recording execution stopped time. Essential container [web-app] stopped at: 2019-09-14 21:29:30.87387509 +0000 UTC m=+10231.607410262
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: sending container change event [web-app]: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 web-app -> STOPPED, Exit 139, , Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: sent container change event [web-app]: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 web-app -> STOPPED, Exit 139, , Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:30Z [INFO] api/task: Updating task desired status to stopped because of container: [web-app]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, TaskStatus: (NONE->RUNNING) Containers: [nginx-proxy (RUNNING->RUNNING),web-app (STOPPED->RUNNING),nginx-proxy-le (NONE->RUNNING),]]
2019-09-14T21:29:30Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (RUNNING->STOPPED),web-app (STOPPED->STOPPED),nginx-proxy-le (NONE->STOPPED),]]
2019-09-14T21:29:30Z [INFO] api/task: Updating task desired status to stopped because of container: [web-app]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (RUNNING->STOPPED),web-app (STOPPED->STOPPED),nginx-proxy-le (NONE->STOPPED),]]
2019-09-14T21:29:30Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy-le]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (RUNNING->STOPPED),web-app (STOPPED->STOPPED),nginx-proxy-le (NONE->STOPPED),]]
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: got container [nginx-proxy-le] event: [STOPPED]
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: handling container change [{STOPPED { <nil> [] <nil> [] map[] 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC 0001-01-01 00:00:00 +0000 UTC {UNKNOWN <nil> 0 }  <nil>} ContainerStatusChangeEvent}] for container [nginx-proxy-le]
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: sending container change event [nginx-proxy-le]: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 nginx-proxy-le -> STOPPED, Known Sent: NONE
2019-09-14T21:29:30Z [INFO] TaskHandler: batching container event: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 web-app -> STOPPED, Exit 139, , Ports [{8080 8080 <IP_ADDRESS> 0}], Known Sent: NONE
2019-09-14T21:29:30Z [INFO] TaskHandler: batching container event: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 nginx-proxy-le -> STOPPED, Known Sent: NONE
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: sent container change event [nginx-proxy-le]: arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073 nginx-proxy-le -> STOPPED, Known Sent: NONE
2019-09-14T21:29:30Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (RUNNING->STOPPED),web-app (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),]]
2019-09-14T21:29:30Z [INFO] api/task: Updating task desired status to stopped because of container: [web-app]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (RUNNING->STOPPED),web-app (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),]]
2019-09-14T21:29:30Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy-le]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (RUNNING->STOPPED),web-app (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),]]
2019-09-14T21:29:30Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (RUNNING->STOPPED),web-app (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),]]
2019-09-14T21:29:30Z [INFO] api/task: Updating task desired status to stopped because of container: [web-app]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (RUNNING->STOPPED),web-app (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),]]
2019-09-14T21:29:30Z [INFO] api/task: Updating task desired status to stopped because of container: [nginx-proxy-le]; task: [awseb-BlogAdminStaging-env-1-wvae7y5qub:14 arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, TaskStatus: (NONE->STOPPED) Containers: [nginx-proxy (RUNNING->STOPPED),web-app (STOPPED->STOPPED),nginx-proxy-le (STOPPED->STOPPED),]]
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: task not steady state or terminal; progressing it
2019-09-14T21:29:30Z [INFO] Managed task [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: waiting for event for task
2019-09-14T21:29:30Z [INFO] Task engine [arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073]: stopping container [nginx-proxy]

docker-event.log:
2019-09-14T21:19:55.504939148Z image tag sha256:838a36e27dbf116cddbe492acd0005e8375bfb3eba9e75586a6eae3faf6cb9f4 (name=amazon/amazon-ecs-agent:latest)
2019-09-14T21:29:00.991002078Z image tag sha256:838a36e27dbf116cddbe492acd0005e8375bfb3eba9e75586a6eae3faf6cb9f4 (name=amazon/amazon-ecs-agent:latest)
2019-09-14T21:29:04.823205995Z volume create ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-certs-9cb190c1f99becd0ff01 (driver=local)
2019-09-14T21:29:04.825940564Z volume create ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-certs-9cb190c1f99becd0ff01 (driver=local)
2019-09-14T21:29:04.826044785Z volume create ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-vhost-fed498e38c9dbdfb8601 (driver=local)
2019-09-14T21:29:04.828876039Z volume create ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-html-aa8ebd87dd9bbd8ab101 (driver=local)
2019-09-14T21:29:14.922282061Z image pull hugozzys/webapp:latest (name=hugozzys/webapp)
2019-09-14T21:29:15.089908831Z container create e25b994e156e150ac96605b56cfe736b877be85ad023a57cc5091822752ccfe5 (com.amazonaws.ecs.cluster=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.container-name=web-app, com.amazonaws.ecs.task-arn=arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, com.amazonaws.ecs.task-definition-family=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.task-definition-version=14, image=hugozzys/webapp:latest, name=ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-web-app-e0fea39ad884a9eaef01)
2019-09-14T21:29:15.205138488Z network connect 5eb7780d6ea115d00e110c67a1b7f27eafecdb5e8ac3b165e9d5142dcfe4b994 (container=e25b994e156e150ac96605b56cfe736b877be85ad023a57cc5091822752ccfe5, name=bridge, type=bridge)
2019-09-14T21:29:15.422121218Z container start e25b994e156e150ac96605b56cfe736b877be85ad023a57cc5091822752ccfe5 (com.amazonaws.ecs.cluster=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.container-name=web-app, com.amazonaws.ecs.task-arn=arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, com.amazonaws.ecs.task-definition-family=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.task-definition-version=14, image=hugozzys/webapp:latest, name=ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-web-app-e0fea39ad884a9eaef01)
2019-09-14T21:29:16.576291709Z container die e25b994e156e150ac96605b56cfe736b877be85ad023a57cc5091822752ccfe5 (com.amazonaws.ecs.cluster=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.container-name=web-app, com.amazonaws.ecs.task-arn=arn:aws:ecs:us-east-2:552900263867:task/0f30e414-f1d6-4fbf-888a-89c39d408896, com.amazonaws.ecs.task-definition-family=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.task-definition-version=14, exitCode=139, image=hugozzys/webapp:latest, name=ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-web-app-e0fea39ad884a9eaef01)
2019-09-14T21:29:16.659453698Z network disconnect 5eb7780d6ea115d00e110c67a1b7f27eafecdb5e8ac3b165e9d5142dcfe4b994 (container=e25b994e156e150ac96605b56cfe736b877be85ad023a57cc5091822752ccfe5, name=bridge, type=bridge)
2019-09-14T21:29:26.550465433Z image pull jwilder/nginx-proxy:latest (maintainer=Jason Wilder<EMAIL_ADDRESS>name=jwilder/nginx-proxy)
2019-09-14T21:29:27.287284666Z volume create ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-certs-9ce9819dc988eedb5600 (driver=local)
2019-09-14T21:29:27.291730711Z volume create ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-certs-9ce9819dc988eedb5600 (driver=local)
2019-09-14T21:29:27.292443400Z volume create ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-vhost-dad59c9bc4b8a4a04900 (driver=local)
2019-09-14T21:29:27.295583142Z volume create ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-html-e0cde1d1e2afd6c56b00 (driver=local)
2019-09-14T21:29:27.530056953Z image pull hugozzys/webapp:latest (name=hugozzys/webapp)
2019-09-14T21:29:27.698518341Z container create 122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618 (com.amazonaws.ecs.cluster=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.container-name=web-app, com.amazonaws.ecs.task-arn=arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, com.amazonaws.ecs.task-definition-family=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.task-definition-version=14, image=hugozzys/webapp:latest, name=ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-web-app-a485accf9acee59c7c00)
2019-09-14T21:29:27.806050284Z network connect 5eb7780d6ea115d00e110c67a1b7f27eafecdb5e8ac3b165e9d5142dcfe4b994 (container=122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618, name=bridge, type=bridge)
2019-09-14T21:29:28.053686289Z container start 122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618 (com.amazonaws.ecs.cluster=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.container-name=web-app, com.amazonaws.ecs.task-arn=arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, com.amazonaws.ecs.task-definition-family=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.task-definition-version=14, image=hugozzys/webapp:latest, name=ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-web-app-a485accf9acee59c7c00)
2019-09-14T21:29:28.275670445Z image pull jwilder/nginx-proxy:latest (maintainer=Jason Wilder<EMAIL_ADDRESS>name=jwilder/nginx-proxy)
2019-09-14T21:29:28.419855361Z volume create ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-vhost-dad59c9bc4b8a4a04900 (driver=local)
2019-09-14T21:29:28.419931291Z volume create ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-certs-9ce9819dc988eedb5600 (driver=local)
2019-09-14T21:29:28.419979685Z volume create ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-html-e0cde1d1e2afd6c56b00 (driver=local)
2019-09-14T21:29:28.493865033Z volume create 098cbb8e8fcb746fd44eb7c30c7a4c8df631e63358535426250cd922fe906009 (driver=local)
2019-09-14T21:29:28.534215320Z container create 83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61 (com.amazonaws.ecs.cluster=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.container-name=nginx-proxy, com.amazonaws.ecs.task-arn=arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, com.amazonaws.ecs.task-definition-family=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.task-definition-version=14, image=jwilder/nginx-proxy, maintainer=Jason Wilder<EMAIL_ADDRESS>name=ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-nginx-proxy-e6e7d78eb8f2879fff01)
2019-09-14T21:29:28.799688022Z network connect 5eb7780d6ea115d00e110c67a1b7f27eafecdb5e8ac3b165e9d5142dcfe4b994 (container=83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, name=bridge, type=bridge)
2019-09-14T21:29:28.804254251Z volume mount ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-vhost-dad59c9bc4b8a4a04900 (container=83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, destination=/etc/nginx/vhost.d, driver=local, propagation=, read/write=true)
2019-09-14T21:29:28.804575387Z volume mount ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-certs-9ce9819dc988eedb5600 (container=83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, destination=/etc/nginx/certs, driver=local, propagation=, read/write=false)
2019-09-14T21:29:28.804810567Z volume mount ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-html-e0cde1d1e2afd6c56b00 (container=83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, destination=/usr/share/nginx/html, driver=local, propagation=, read/write=true)
2019-09-14T21:29:28.805055728Z volume mount 098cbb8e8fcb746fd44eb7c30c7a4c8df631e63358535426250cd922fe906009 (container=83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, destination=/etc/nginx/dhparam, driver=local, propagation=, read/write=true)
2019-09-14T21:29:29.209162985Z container start 83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61 (com.amazonaws.ecs.cluster=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.container-name=nginx-proxy, com.amazonaws.ecs.task-arn=arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, com.amazonaws.ecs.task-definition-family=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.task-definition-version=14, image=jwilder/nginx-proxy, maintainer=Jason Wilder<EMAIL_ADDRESS>name=ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-nginx-proxy-e6e7d78eb8f2879fff01)
2019-09-14T21:29:30.525947015Z container die 122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618 (com.amazonaws.ecs.cluster=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.container-name=web-app, com.amazonaws.ecs.task-arn=arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, com.amazonaws.ecs.task-definition-family=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.task-definition-version=14, exitCode=139, image=hugozzys/webapp:latest, name=ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-web-app-a485accf9acee59c7c00)
2019-09-14T21:29:30.755960849Z network disconnect 5eb7780d6ea115d00e110c67a1b7f27eafecdb5e8ac3b165e9d5142dcfe4b994 (container=122b9daa0873a9b82a9a5adc664e5e91974679465b7cfdc4d3827a0ee7f35618, name=bridge, type=bridge)
2019-09-14T21:29:30.944310351Z container kill 83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61 (com.amazonaws.ecs.cluster=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.container-name=nginx-proxy, com.amazonaws.ecs.task-arn=arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, com.amazonaws.ecs.task-definition-family=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.task-definition-version=14, image=jwilder/nginx-proxy, maintainer=Jason Wilder<EMAIL_ADDRESS>name=ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-nginx-proxy-e6e7d78eb8f2879fff01, signal=15)
2019-09-14T21:29:31.219182084Z container die 83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61 (com.amazonaws.ecs.cluster=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.container-name=nginx-proxy, com.amazonaws.ecs.task-arn=arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, com.amazonaws.ecs.task-definition-family=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.task-definition-version=14, exitCode=2, image=jwilder/nginx-proxy, maintainer=Jason Wilder<EMAIL_ADDRESS>name=ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-nginx-proxy-e6e7d78eb8f2879fff01)
2019-09-14T21:29:31.370496469Z network disconnect 5eb7780d6ea115d00e110c67a1b7f27eafecdb5e8ac3b165e9d5142dcfe4b994 (container=83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, name=bridge, type=bridge)
2019-09-14T21:29:31.417660137Z volume unmount 098cbb8e8fcb746fd44eb7c30c7a4c8df631e63358535426250cd922fe906009 (container=83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, driver=local)
2019-09-14T21:29:31.422435738Z volume unmount ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-vhost-dad59c9bc4b8a4a04900 (container=83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, driver=local)
2019-09-14T21:29:31.422516175Z volume unmount ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-certs-9ce9819dc988eedb5600 (container=83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, driver=local)
2019-09-14T21:29:31.422555640Z volume unmount ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-html-e0cde1d1e2afd6c56b00 (container=83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61, driver=local)
2019-09-14T21:29:31.431089629Z container stop 83605b3d1bd91bd28f08a0d2e68b2fe70180f1a89d3d82743986486f318adf61 (com.amazonaws.ecs.cluster=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.container-name=nginx-proxy, com.amazonaws.ecs.task-arn=arn:aws:ecs:us-east-2:552900263867:task/e8232943-105b-40e8-a421-710abea4e073, com.amazonaws.ecs.task-definition-family=awseb-BlogAdminStaging-env-1-wvae7y5qub, com.amazonaws.ecs.task-definition-version=14, image=jwilder/nginx-proxy, maintainer=Jason Wilder<EMAIL_ADDRESS>name=ecs-awseb-BlogAdminStaging-env-1-wvae7y5qub-14-nginx-proxy-e6e7d78eb8f2879fff01)
2019-09-14T21:29:35.009539024Z image pull jrcs/letsencrypt-nginx-proxy-companion:latest (maintainer=Yves Blusseau<EMAIL_ADDRESS>(@blusseau), name=jrcs/letsencrypt-nginx-proxy-companion)

Was anyone able to solve this? Experiencing this same issue, one year later

@Hugozys @milenazuccarelli unfortunately there isn't anything we can do from this project perspective to solve this, as explained before the issues lies between docker-gen and the newest ECS AMI.

@Feelthewind have you found a solution. I have exactly the same issue. what do you use now ?

I have a little bit of a workaround in place, and it seems to work (at first glance). Essentially it involves getting the /etc/nginx/conf.d/default.conf which is autogenerated by nginx-proxy container and manually authoring the upstream section(s) to accurately reference whatever webapp(s) you are hosting. Prior to doing this is is advantageous to add "links" from nginx-proxy to your app(s) in Dockerrun.aws.json so that the docker network is set up between the two containers and an alias for the webapp is generated within the proxy. Then, I ensure that this default.conf is always used by the nginx-proxy by setting /etc/nginx/conf.d/ as a read only volume on the proxy. Finally, I use an .ebextensions script to author the default.conf into place.
Dockerrun.aws.json
...
  "volumes": [
    {
      "name": "home-ec2-user-certs",
      "host": {
        "sourcePath": "/home/ec2-user/certs"
      }
    },
    {
      "name": "etc-nginx-vhost-d",
      "host": {
        "sourcePath": "/etc/nginx/vhost.d"
      }
    },
    {
      "name": "usr-share-nginx-html",
      "host": {
        "sourcePath": "/usr/share/nginx/html"
      }
    },
    {
      "name": "var-run-docker-sock",
      "host": {
        "sourcePath": "/var/run/docker.sock"
      }
    },
    {
      "name": "nginx-config-overwrite",
      "host": {
        "sourcePath": "/etc/nginx/conf.d/"
      }
    }
  ],
"containerDefinitions": [
    {
      "name": "nginx-proxy",
      "image": "jwilder/nginx-proxy",
      "essential": true,
      "memoryReservation": 128,
      "dockerLabels": {
        "com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy": "true"
      },
      "portMappings": [
        {
          "containerPort": 80,
          "hostPort": 80
        },
        {
          "containerPort": 443,
          "hostPort": 443
        }
      ],
      "links": [
        "prod-app"
      ],
      "mountPoints": [
        {
          "sourceVolume": "home-ec2-user-certs",
          "containerPath": "/etc/nginx/certs",
          "readOnly": true
        },
        {
          "sourceVolume": "etc-nginx-vhost-d",
          "containerPath": "/etc/nginx/vhost.d"
        },
        {
          "sourceVolume": "usr-share-nginx-html",
          "containerPath": "/usr/share/nginx/html"
        },
        {
          "sourceVolume": "var-run-docker-sock",
          "containerPath": "/tmp/docker.sock",
          "readOnly": true
        },
        {
          "sourceVolume": "nginx-config-overwrite",
          "containerPath": "/etc/nginx/conf.d",
          "readOnly": true
        }
      ]
    },
...

/etc/nginx/conf.d/default.conf
...
upstream yyy.xxxxx.com {
  # I'm filling this part in manually!!
  server prod-app:8000;
  keepalive 256;
}
...

.ebextensions/05_nginx_config.config
files:
  "/etc/nginx/conf.d/default.conf":
    mode: "000644"
    owner: root
    group: root
    content: |
      map $http_x_forwarded_proto $proxy_x_forwarded_proto {
        default $http_x_forwarded_proto;
        ''      $scheme;
      }
      map $http_x_forwarded_port $proxy_x_forwarded_port {
        default $http_x_forwarded_port;
        ''      $server_port;
      }
      map $http_upgrade $proxy_connection {
        default upgrade;
        '' close;
       ...

The workaround I mentioned before was not very reliable so I sought to correct the problem more permanently.
Use my fork of nginx-proxy in your deployment (until my pull request is accepted) to fix this:
Dockerrun.aws.json
...
"containerDefinitions": [
    {
      "name": "nginx-proxy",
      "image": "thismatters/nginx-proxy",    <--- that is the change!
      "essential": true,
      "memoryReservation": 128,
      "dockerLabels": {
        "com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy": "true"
      },
      "portMappings": [
        {
          "containerPort": 80,
          "hostPort": 80
        },
        {
          "containerPort": 443,
          "hostPort": 443
        }
      ],
      "links": [
        "prod-app"
      ],
      "environment": [{
        "name": "NGINX_PROXY_CONTAINER",
        "value": "true"
      }],
      "mountPoints": [
        {
          "sourceVolume": "home-ec2-user-certs",
          "containerPath": "/etc/nginx/certs",
          "readOnly": true
        },
        {
          "sourceVolume": "etc-nginx-vhost-d",
          "containerPath": "/etc/nginx/vhost.d"
        },
        {
          "sourceVolume": "usr-share-nginx-html",
          "containerPath": "/usr/share/nginx/html"
        },
        {
          "sourceVolume": "var-run-docker-sock",
          "containerPath": "/tmp/docker.sock",
          "readOnly": true
        }
      ]
    },
    {
      "name": "nginx-proxy-letsencrypt",
      "image": "jrcs/letsencrypt-nginx-proxy-companion",
      "essential": true,
      "memoryReservation": 128,
      "volumesFrom": [
        {
          "sourceContainer": "nginx-proxy"
        }
      ],
      "mountPoints": [
        {
          "sourceVolume": "home-ec2-user-certs",
          "containerPath": "/etc/nginx/certs"
        },
        {
          "sourceVolume": "var-run-docker-sock",
          "containerPath": "/var/run/docker.sock",
          "readOnly": true
        }
      ]
    },
...

While working on GitHub Actions I think I found (and patched) the issue in docker-gen that prevent the whole stack from working on Amazon ECS.
I'm trying to reach @jwilder to discuss docker-gen maintenance.
In the meantime, if anyone is interested in testing if this patch actually fixes nginx-proxy / docker-gen on Amazon ECS, I can provide Example Dockerfile that will build patched images.