Optimizing Node.js Code Coverage With NYC in Docker Containers | HackerNoon
Briefly

Running NYC locally is straightforward with a simple command: "start": "nyc node ./dist/main.js". However, there are more stages involved in getting support within Docker.
In a Docker container, the CMD or ENTRYPOINT process runs as PID 1, which is responsible for handling system signals. This is crucial for proper signal forwarding.
When you press Ctrl+C, Docker sends a SIGINT signal to the PID 1 process. If sh is still the PID 1 process within the container, it might not forward the signal appropriately.
A simple trap signal and passing it to child processes should solve the issue of signal forwarding, preventing zombie processes and ensuring a responsive container.
Read at Hackernoon
[
]
[
|
]