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

Cannot send SIGTERM to service in Docker container #187

Open
arteymix opened this issue Jul 26, 2016 · 3 comments
Open

Cannot send SIGTERM to service in Docker container #187

arteymix opened this issue Jul 26, 2016 · 3 comments
Assignees
Labels
Milestone

Comments

@arteymix
Copy link
Member

We have right to the following error when sending a SIGTERM to a running docker container.

GLib-WARNING **: poll(2) failed due to: Operation not permitted.

@arteymix arteymix added the bug label Jul 26, 2016
@arteymix arteymix added this to the 0.3.0 milestone Jul 26, 2016
@arteymix arteymix self-assigned this Jul 26, 2016
@arteymix
Copy link
Member Author

I investigated this and it seems we can still send a SIGTERM via docker stop, it just doesn't play well via the pseudo-TTY.

This can wait for a patch release.

@arteymix arteymix modified the milestones: 0.3.0, 0.3.7 Feb 22, 2017
@notanimposter
Copy link

notanimposter commented Feb 27, 2022

^C works fine when my Dockerfile contains:

ENTRYPOINT /app/bin/app --any --port 3003

but it doesn't do anything when my Dockerfile contains:

ENTRYPOINT ["/app/bin/app", "--any", "--port", "3003"]

@arteymix
Copy link
Member Author

The difference here is that your option implies using a shell for running the command. Ideally VSGI should handle SIGTERM properly.

@arteymix arteymix modified the milestones: 0.3.7, 0.3.19 Sep 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants