-
-
Notifications
You must be signed in to change notification settings - Fork 158
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
st2actionrunner: Missing entrypoint.d #205
Comments
I guess in terms of Docker image immutability it's an anti-pattern to include some kind of time-consuming operation (like package installation, etc) during the container startup as it affects the time ST2 cluster becomes ready and there is no guarantee that command will succeed which may bring you a failed cluster and reproducibility issue. From the production standpoint it's indeed better to build your own st2actionrunner images. From the other side I understand the reason that it's not always makes sense to build the new images from scratch in some environments and K8s has As a workaround you could overwrite the CMD aka |
Describe the problem
Preview version of st2docker enabled entrypoint customization allowing a to add additionnal binairies and configuration files, without requiring to build a devired image
This feature has diseapered with the 3.3.0 release and is not documented in the release note.
What is the recommended approach for people that want to customize the st2actionrunner ?
Versions
To Reproduce
If necessary, please specify steps to reproduce the behavior.
Running any Packs that require additionnal binaries (Terraform, Salt, Ansible, etc)
The text was updated successfully, but these errors were encountered: