fix(server): handle kernel signals by including tini

[PixnBits]

Description

Wrap the Node.js process with the tini init wrapper. This enables proper kernel signal handling inside the container, removing the need for forceful shutdowns (e.g. $ docker ps; docker kill <container-id>).

This adds 96kB to the image size.

We may later be able to remove src/server/shutdown.js if the Babel issue is resolved (it's been a number of years). Though, it might serve has a failure handling in the event we miss something that keeps Node.js running (e.g. a setInterval without .unref()).

Motivation and Context

Node.js was not designed to run as PID 1 which leads to unexpected behaviour when running inside of Docker. For example, a Node.js process running as PID 1 will not respond to SIGINT (CTRL-C) and similar signals. ...
You can...include Tini directly in your Dockerfile, ensuring your process is always started with an init wrapper.

https://github.com/nodejs/docker-node/blob/main/docs/BestPractices.md#handling-kernel-signals

How Has This Been Tested?

I've built the image locally, used it via @americanexpress/one-app-runner (npm start -- --offline --docker-image=sha256:...) and upon CTRL+C the container stops (due to the Node.js process ending).

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)
• Dependency update
• Security update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• These changes should be applied to a maintenance branch. (fix(server): handle kernel signals by including tini #1388)
• This change requires cross browser checks.
• Performance tests should be ran against the server prior to merging.
• This change impacts caching for client browsers.
• This change impacts HTTP headers.
• This change adds additional environment variable requirements for One App users.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using One App?

Don't have to wait 10,000ms for the shutdown check to run. Should also be more graceful and faster shutdowns in production.

[github-actions]

Size Change: 0 B

Total Size: 232 kB

ℹ️ View Unchanged

Filename	Size
./build/app/app.js	38.2 kB
./build/app/app~vendors.js	129 kB
./build/app/runtime.js	5.64 kB
./build/app/service-worker-client.js	5.46 kB
./build/app/vendors.js	54.1 kB

_{compressed-size-action}

[10xLaCroixDrinker]

This breaks the start command when running in the repo.

$ npm start

> @americanexpress/[email protected] start
> scripts/start.sh

/sbin/tini -- node --dns-result-order ipv4first --no-experimental-fetch --require=dotenv/config lib/server/index.js
scripts/start.sh: line 39: /sbin/tini: No such file or directory
scripts/start.sh: line 39: exec: /sbin/tini: cannot execute: No such file or directory

[PixnBits]

good catch! it's also probably better for tini to be the entrypoint rather than deferred to a script file so it can manage all the child processes
updated in fe13e5a