-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
docker stop not triggering shutdown signal [v20] #2029
Comments
That looks like npm/cli#6684 (comment); so, the fix is to update |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Expected Behavior
docker stop command should trigger SIGTERM signal
Current Behavior
For node:18.16.1-alpine3.18 and below the SIGTERM is received. But all above versions [I tried node:20.11.0-alpine3.18] its not received. Used command with init.
Steps to Reproduce
For both the version follow below steps
Additional Information
Steps and commands followed along with its output
NODE VERSION 18.16.1
NODE VERSION 20
Please see points 3 and 4 for both the outputs above.
For v20 it does not log the signal and gets forcefully shutdown with exit code 137
For v18 it logs the signal and the application closes with the expected exit code.
The text was updated successfully, but these errors were encountered: