Laurent Goderre

@ShadabFaiz are you using the `18-alpine` tag? If so, 2 months ago, the alpine version that `alpine` points to was changed from 3.18 to 3.19 which could have cause a...

Should we close this? Alpine 3.16 hasn't been supported for almost a year

The fixed mentioned above does work Before: `docker run --rm -it --read-only --entrypoint npm node:18-alpine ping --loglevel=verbose` ``` npm verb cli /usr/local/bin/node /usr/local/bin/npm npm info using [email protected] npm info using...

Alternatively, you can use a custom entrypoint like this: ```bash #!/usr/bin/env bash corepack enable su - node && corepack prepare && pnpm install && $@ ``` ```sh docker run --rm...

It sounds like the path gets overridden and doesn't include `/use/local/bin`?

LIkely related to https://github.com/nodejs/node/issues/42888

For the original use case, an init container would serve this much better. You could have an image with your data copied in and use `mongorestore` with the hostname of...

This fixes it: #76. Could you merge an publish 1.3.1?

Nevermind, the current unrelease fixed is better.

@sjpotter can you confirm that the redis process is PID1 when it doesn't get the SIGTERM?