How does a Strapi docker container handle SIGTERM, SIGSTOP, and SIGKILL?

marc · July 30, 2021, 9:49am

System Information

Strapi Version: v3.6.5 (docker container)
Operating System: Linux
Database: MongoDB Atlas
Node Version: 14.17.4
Yarn Version: 1.22.10

I have a Strapi docker container whose base image is strapi/base:14. However I wonder I looked into this writing :

and wondered how a Strapi docker container handles SIGSTOP, SIGTERM, and SIGKILL.

Any feedback is appreciated.

eatanasov · April 26, 2024, 9:55am

Hello!

I hope this bit of the strapi repo will shed some light.

github.com

strapi/strapi/blob/a76a2ee7a9a66bc0233e678ca062086c34855a5c/packages/core/strapi/src/utils/signals.ts#L16


      
            // For unknown reasons, we receive signals 2 times.
            // As a temporary fix, we ignore the signals received after the first one.
          
            const terminateStrapi = async () => {
              if (!signalReceived) {
                signalReceived = true;
                await strapi.destroy();
                process.exit();
              }
            };
          
            ['SIGTERM', 'SIGINT'].forEach((signal) => {
              process.on(signal, terminateStrapi);
            });
          };

Cheer!