docker.run closes the streams when the container stops if Tty: false

[kevinlul]

Following the example in the README to separate stdout and stderr for docker.run, after the promise resolves or the callback is called, the streams are closed. This shuts off the entire process' outputs. A subsequent call to docker.run in the same fashion will eventually crash the process with ERR_STREAM_WRITE_AFTER_END, since stdout and stderr were closed.

[adamburgess]

Had this same problem...
easy fix is to use a passthrough so the final stream isn't closed:

const stdout = new stream.PassThrough();
stdout.pipe(process.stdout, { end: false });

docker.run(..., [stdout, stdout], ...);

this doesn't really seem to be dockerode's fault fyi, process.stdout/err don't get closed when you pipe to them, only when you explicitly call end(). Like, even if you use

stdout.pipe(process.stdout, { end: true })

stdout will still stay open... nodejs/node#7606 (comment)

[kevinlul]

At least the README should be updated, maybe to match your sample, because if example usage ends up causing bad behaviour then it makes for a poor example.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Open a new issue if needed.