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
However, after switching from using tini in our containers to embedded initProcessEnabled docker parameter I have discovered the following issue:
after updating any ECS service with ecs-goploy (and ecs-deploy too) linuxParameters section of task definition (which contains the needed initProcessEnabled parameter) is set to null. See example below.
Hmm... ecs-goploy does not change linuxParameters in current task definition. Probably AWS API updates the section to default value when create a new task definition.
So we have to override it with current value.
Hi! Thank you for developing such a great tool.
However, after switching from using
tini
in our containers to embeddedinitProcessEnabled
docker parameter I have discovered the following issue:after updating any ECS service with
ecs-goploy
(andecs-deploy
too)linuxParameters
section of task definition (which contains the neededinitProcessEnabled
parameter) is set tonull
. See example below.before ecs-goploy:
after updating the service:
The text was updated successfully, but these errors were encountered: