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
By providing an env variable like ECS_DOCKER_RUNTIME we could make the configuration easier by building an AMI based on Amazon Linux (1, 2 or 2023), installing sysbox and then setting echo "ECS_DOCKER_RUNTIME=sysbox-runc" >> /etc/ecs/ecs.conf.
Without that variable we're forced to start and manage the ECS agent manually as well as setting up network configuration with iptables.
The text was updated successfully, but these errors were encountered:
Hi @mliezun. Thanks for creating this issue and sorry for the delay in our response. I will move transfer this issue to our feature requests repository.
Summary
Support for alternative docker runtimes by specifying
ECS_DOCKER_RUNTIME
.Description
To be able to use custom docker runtimes like sysbox is necessary to do some pretty involved configurations as showed in this post: https://aws.amazon.com/pt/blogs/aws-brasil/utilizando-runtimes-customizados-no-amazon-ecs/.
By providing an env variable like
ECS_DOCKER_RUNTIME
we could make the configuration easier by building an AMI based on Amazon Linux (1, 2 or 2023), installing sysbox and then settingecho "ECS_DOCKER_RUNTIME=sysbox-runc" >> /etc/ecs/ecs.conf
.Without that variable we're forced to start and manage the ECS agent manually as well as setting up network configuration with iptables.
The text was updated successfully, but these errors were encountered: