standalone mode in docker can't be killed by SIGTERM

[zfben]

Astro Info

the docker image based on node:lts-alpine

Describe the Bug

1. build a docker image
2. start it
3. stop it by docker kill --signal=SIGTERM

the server doesn't stop.

What's the expected result?

stop the server and container.

Link to Minimal Reproducible Example

https://idx.google.com/just-the-basics-5506607

Participation

• I am willing to submit a pull request for this issue.

[kaytwo]

Your idx gave me an auth error, but I ran into the same problem, here's what I learned:

• I had this issue with the dev server as well, however switching to this command in my compose file fixed it: command: sh -c "npm install && exec npm run dev" - this causes sh to not eat the SIGINT and shut down cleanly.
• I was able to reproduce this and tried both the "exec style" and "shell style" invocations in my Dockerfile, however both seemed to ignore SIGTERM.
• They don't, however, ignore SIGINT, so setting STOPSIGNAL SIGINT in the Dockerfile "fixed" the problem for me.

I don't know whether there is anything in the innards of the node server that will break because we're sending SIGINT instead of SIGTERM, but I doubt it.

[zfben]

@kaytwo I switch to middleware mode and handle signal manully now. maybe you can do it too.