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
The amzn2 ECS images use a proper systemd unit to start docker instead of a sysvinit script.
The /etc/sysconfig/docker file is referenced for environment variables but the file isn't sourced, as in the way the sysvinit scripts work, so that appended line doesn't result in the OPTIONS envvar being built up, but rather being set to that. This then causes the docker service to fail on reboot of the instance or restart of the service with the error "dockerd accepts no arguments".
This is not noticed normally because the next line in the template /etc/init.d/docker restart is invalid in the amzn2 systemd instances so it doesn't actually restart docker and encounter this broken config .... you only get caught out by it on a service restart or a reboot.
In our use of this module we're now doing a sed -i '/OPTIONS="${OPTIONS}/d' /etc/sysconfig/docker to avoid this particular problem.
The text was updated successfully, but these errors were encountered:
The user_data.tpl template appends the following line to /etc/sysconfig/docker:
The amzn2 ECS images use a proper systemd unit to start docker instead of a sysvinit script.
The /etc/sysconfig/docker file is referenced for environment variables but the file isn't sourced, as in the way the sysvinit scripts work, so that appended line doesn't result in the OPTIONS envvar being built up, but rather being set to that. This then causes the docker service to fail on reboot of the instance or restart of the service with the error "dockerd accepts no arguments".
This is not noticed normally because the next line in the template
/etc/init.d/docker restart
is invalid in the amzn2 systemd instances so it doesn't actually restart docker and encounter this broken config .... you only get caught out by it on a service restart or a reboot.In our use of this module we're now doing a
sed -i '/OPTIONS="${OPTIONS}/d' /etc/sysconfig/docker
to avoid this particular problem.The text was updated successfully, but these errors were encountered: