---
title: "Discussion on \"Why your Node.js container ignores docker stop: PID 1, npm start and SIGTERM\" | Hashnode"
description: "Discussion on \"Why your Node.js container ignores docker stop: PID 1, npm start and SIGTERM\". You run docker stop or docker compose stop and the container just sits there for a while before it goes away. The shutdown code in your Node.js app never logs a thing. Usually the signal never reached"
url: "https://hashnode.com/posts/why-your-node-js-container-ignores-docker-stop-pid-1-npm-start-and-sigterm/6aec9db626d0cb6012bcf913"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why your Node.js container ignores docker stop: PID 1, npm start and SIGTERM](https://shipkit.hashnode.dev/why-your-node-js-container-ignores-docker-stop-pid-1-npm-start-and-sigterm?utm_source=hashnode&utm_medium=feed)

You run docker stop or docker compose stop and the container just sits there for a while before it goes away. The shutdown code in your Node.js app never logs a thing. Usually the signal never reached

6d ago · 6 min read · shipkit.hashnode.dev  
Read the article

-   [#docker](https://hashnode.com/tag/docker)
-   [#nodejs](https://hashnode.com/tag/nodejs)
-   [#devops](https://hashnode.com/tag/devops)
-   [#containers](https://hashnode.com/tag/containers)

## Written by

[ShipKit](https://hashnode.com/@shipkit)

@shipkit

  
[View profile](https://hashnode.com/@shipkit)

Teaching notes on GitHub Actions and Docker from ShipKit.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.