Node v5.x.x does not exit on Ctrl-C in Docker container

[adam-beck]

server.js

var http = require('http');
var server = http.createServer();


server.listen(3000, function() {
  console.log('listening on port 3000...');
});

docker run --rm -it -v /home/foo/repos/test/server.js:/usr/test/server.js -w /usr/test node node server.js

You are unable to kill the server by using Ctrl-C anymore. I've tried testing this with an older version of node (0.10.41) and it seems to be working properly. I am able to use docker stop $CONTAINER_ID and it will stop the container.

May be something similar to this

[evanlucas]

There is another issue (somewhere in the archive repo) that goes into detail on why that is the intended behavior (I'm searching for it). But, to work around, you can add listeners for those signals and then call process.exit()

[chrisdopuch]

I was able to reproduce this problem using Node 5.2.0, and I also reproduced the correct behavior with Node 0.10.41.

@evanlucas your workaround does work great, added the following to @adam-beck 's code and was able to end the process in Node 5.2.0 with Ctrl-c

process.on('SIGINT', function() {
    process.exit();
});

Docker version 1.8.2
docker-machine version 0.4.1
OSX Yosemite 10.10.5

[adam-beck]

The above code worked. Thanks @evanlucas & @chrisdopuch.

[samsalisbury]

Should this issue be closed @adam-beck @evanlucas @chrisdopuch ? It seems like broken behaviour, since node usually exits on SIGINT on Mac, why should it need to have explicit handlers registered when running inside a Ubuntu-14 Docker container? It means that Node code is not portable in this regard, which seems like an odd decision if it is really intended.

[chrisdopuch]

I agree @samsalisbury, and I would also still like to see this issue resolved.

[MylesBorins]

/cc @nodejs/ctc

[samsalisbury]

Also note that this is broken at least as early as node 4.2.3, which is what I'm using now, and probably earlier.

[misterdjules]

@evanlucas Were you looking for nodejs/node-v0.x-archive#9131, as indicated at the bottom of the issue's description (maybe edited after your comment was posted)?

[MylesBorins]

nodejs/node-v0.x-archive#9131 (comment) seems to do a really good job of describing what is happening, and why this appears to be an issue with docker not node. The issue tracking this on docker was closed as fixed, and it seems if process.on('sigint') is firing than perhaps docker is passing the SIGINT to pid 1 as expected.

I think someone with a bit more docker understanding needs to take a peak @nodejs/docker

[evanlucas]

Thanks @misterdjules for the link. I was thinking there was another issue, but I have been unable to find it. I agree with @thealphanerd that the description in the previous issue explains it pretty well. But, since @indutny signed off on the commit that changed this behavior, perhaps he can shed some light on this.