Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nuances to config this properly #1

Open
rClark-qubeyond opened this issue Apr 1, 2024 · 0 comments
Open

Nuances to config this properly #1

rClark-qubeyond opened this issue Apr 1, 2024 · 0 comments

Comments

@rClark-qubeyond
Copy link

Thanks for the great helper function, though I've found two instances where this still may not work as expected, maybe something for the docs or a minor code tweak.

  1. we happened to have tasks configured to use LogConfig awslogs for the container. By default, this driver uses 'mode":"blocking" which resulted in containers failing to relaunch and exiting with code 128 due to failure to reach the Cloudwatch services. Changing this to "mode":"non-blocking" in the task def seemed to resolve.

  2. in another case, a multi-container task seems to exit on shutdown/reboot of the external instance to status "exited". This status apparently is not picked up with a restart policy of "on-failure". Changing the Python script to assign restart policy "always" in an offline scenario properly picked things up on reboot and reverted once online again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant