Node 18.19.0 in docker container does not exit when unhandled promise rejection occured.

[MengLi619]

Version

18.19.0

Platform

Docker (node:18.19.0-alpine3.17)

Subsystem

No response

What steps will reproduce the bug?

We depend on nodejs process exit and restart to complete the startup process. But nodejs in the container (node:18.19.0-alpine3.17) does not exit but throws a warning.

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

How often does it reproduce? Is there a required condition?

Every time

What is the expected behavior? Why is that the expected behavior?

Node process should exit, this should be a default behavior after node15.

What do you see instead?

Node does not exit but throws a warning:

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

Additional information

No response