-
Notifications
You must be signed in to change notification settings - Fork 506
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
Non-terminal signals are killing containers running with --init flag #204
Comments
I think this means your process doesn't have a handler for |
Hm, I didn't know SIGUSRs are terminating by default, that's why used a random web server as example, sorry. But initially this issue happened with my own image which has a SIGUSR2 handler. I've created a POC repo: https://github.com/rayrapetyan/test_sig. Steps to reproduce the issue:
and process continues running as expected. Now run cmd.sh from container:
Send SIGUSR2: Expected: cmd.sh running inside a docker container should receive and handle a signal and continue running. Now after looking into how cmd.sh is running inside a container: |
Works when running as: |
Description
This looks like invalid behavior: docker-init (tini) process should proxy signals to child processes.
Instead any container started with --init flag can be killed with a non-terminal signal (e.g. SIGUSR2, SIGHUP etc).
Reproduce
Expected behavior
Container continues to run (as it does when started without --init flag)
Actual
Container is being stopped and killed
docker version
docker info
The text was updated successfully, but these errors were encountered: