-
Notifications
You must be signed in to change notification settings - Fork 9
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
Process received a SIGTERM signal #14
Comments
Hi Thomas, that sounds strange, SIGTERM is normally a hard kill by the host, so I'm not sure what could happen there. As I'm not so much into k8s, but here is an idea why this could happen: The healthcheck goes bad / is not doing it a k8s way and kills the process before the healthcheck reports a heatly service? Try to remove https://github.com/adrianrudnik/mjml-server/blob/develop/Dockerfile#L23 to L24 and deploy that service and see if it stays alive. Otherwise I would suspect a misconfigured service, like not auto-upping it or downscaling it to zero? Not sure that makes sense. Feel free to post a minimal config I could start of with MicroK8s if you can, never did it myself, just doing docker :) |
Hi Thomas, I just reviewed some parts and improved the healthcheck (and made that toggleable). Can you try the image The new ENV available is |
Thanks a lot for your help on that. We found out why the container keep restarting to finally crashLoopBack while deploying on k8s environment. Once again thanks for your reply, |
Hello @adrianrudnik
Thanks a lot for your work :)
It works fine locally, and we try to deploy it on kubertes.
But the process always received a SIGTERM signal.
Any idea how we can debug it ?
here the logs of the container :
Thank you for your help,
Thomas.
The text was updated successfully, but these errors were encountered: