You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a container instance is draining, the boto3 api for list-tasks defaults to include all tasks that have a desiredStatus of RUNNING. However, the api (as of 2019-03-06) will return a desiredStatus of STOPPED before the container has exited on the instance. If the ECS cluster has a longer than default (30 seconds) ECS_CONTAINER_STOP_TIMEOUT, and your container takes a while to clean up and exit, this template will complete complete the Auto Scaling Lifecycle Hook before the container exits.
This leads to hard-to-diagnose issues where the container instance (and its logs) are terminated before expected.
Is there a way to run an equivalent of docker ps from the Lambda job to confirm a task has exited?
The text was updated successfully, but these errors were encountered:
When a container instance is draining, the boto3 api for
list-tasks
defaults to include all tasks that have adesiredStatus
ofRUNNING
. However, the api (as of 2019-03-06) will return adesiredStatus
ofSTOPPED
before the container has exited on the instance. If the ECS cluster has a longer than default (30 seconds)ECS_CONTAINER_STOP_TIMEOUT
, and your container takes a while to clean up and exit, this template will complete complete the Auto Scaling Lifecycle Hook before the container exits.This leads to hard-to-diagnose issues where the container instance (and its logs) are terminated before expected.
Is there a way to run an equivalent of
docker ps
from the Lambda job to confirm a task has exited?The text was updated successfully, but these errors were encountered: