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

Exit 137 on docker stop #239

Closed
se7entyse7en opened this issue Aug 6, 2019 · 0 comments · Fixed by #271
Closed

Exit 137 on docker stop #239

se7entyse7en opened this issue Aug 6, 2019 · 0 comments · Fixed by #271
Assignees

Comments

@se7entyse7en
Copy link
Contributor

When the container is stopped, the return code is 137. Most probably this means that SIGTERM is not handled by sourced-ui, so the SIGTERM signal sent by docker-stop it's actually ignored, and a kill is sent after the timeout. The reason is that in the container the process is running with pid 1.

Sources:

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

Successfully merging a pull request may close this issue.

2 participants