Can't run "run" script despite following setup docs

[klnsv]

Description

I followed the instructions provided in the documentation for mermaid setup Link to Doc

When I run ./run pnpm install, it creates and builds the container and throws some error at the end.

Terminal Output:

$ ./run pnpm install
[+] Creating 4/1
 ✔ Network mermaid_default      Created                                                                            0.1s
 ✔ Volume "mermaid_root_local"  Created                                                                            0.0s
 ✔ Volume "mermaid_root_npm"    Created                                                                            0.0s
 ✔ Volume "mermaid_root_cache"  Created                                                                            0.0s
[+] Building 18.5s (8/8) FINISHED                                                                        docker:default
 => [mermaid internal] load build definition from Dockerfile                                                       0.1s
 => => transferring dockerfile: 358B                                                                               0.0s
 => [mermaid internal] load metadata for docker.io/library/node:22.12.0-alpine3.19@sha256:40dc4b415c17b85bea9be05  5.7s
 => [mermaid internal] load .dockerignore                                                                          0.1s
 => => transferring context: 2B                                                                                    0.0s
 => [mermaid 1/3] FROM docker.io/library/node:22.12.0-alpine3.19@sha256:40dc4b415c17b85bea9be05314b4a753f45a4e171  8.4s
 => => resolve docker.io/library/node:22.12.0-alpine3.19@sha256:40dc4b415c17b85bea9be05314b4a753f45a4e1716bb31c01  0.1s
 => => sha256:f81c161f5fb8bdd588bd96e396a885e842bbb7a044983d3851055dc83132da13 445B / 445B                         0.5s
 => => sha256:cef716d39f61c1099bc1cc0b32efae3753e57b300cbbd6ec1ed1b9a15b92464c 1.39MB / 1.39MB                     1.1s
 => => sha256:d12adb5e728bd8dbc3c33371ec183da2c768df3a87e337d530bcf23ccff15450 50.09MB / 50.09MB                   7.0s
 => => sha256:a7cd7d9a21440da0d765f2989d75f069adf9b3463a765421a0590bca720920d4 3.42MB / 3.42MB                     1.6s
 => => extracting sha256:a7cd7d9a21440da0d765f2989d75f069adf9b3463a765421a0590bca720920d4                          0.1s
 => => extracting sha256:d12adb5e728bd8dbc3c33371ec183da2c768df3a87e337d530bcf23ccff15450                          0.9s
 => => extracting sha256:cef716d39f61c1099bc1cc0b32efae3753e57b300cbbd6ec1ed1b9a15b92464c                          0.1s
 => => extracting sha256:f81c161f5fb8bdd588bd96e396a885e842bbb7a044983d3851055dc83132da13                          0.0s
 => [mermaid 2/3] RUN corepack enable     && corepack enable pnpm                                                  0.7s
 => [mermaid 3/3] RUN apk add --no-cache git~=2.43     && git config --add --system safe.directory /mermaid        2.1s
 => [mermaid] exporting to image                                                                                   1.1s
 => => exporting layers                                                                                            0.7s
 => => exporting manifest sha256:07f8fd27a3b562cc20634fc9aa458588e4dee821b7a21e9cd75dcab9d1ac73a1                  0.0s
 => => exporting config sha256:61d78c929e7a312c619c01cdc173d0e513d43166e48be46e1c71a9fd3e9a6a27                    0.0s
 => => exporting attestation manifest sha256:e46e981f7ae3390f91c25c30b1eab18e7e40935aa95cf1ec9e44e5f79ec580c7      0.1s
 => => exporting manifest list sha256:c261931cc26b2606b20e0379fa6a9e68b8be2a8fabc3b363e24af06285111294             0.0s
 => => naming to docker.io/library/mermaid-mermaid:latest                                                          0.0s
 => => unpacking to docker.io/library/mermaid-mermaid:latest                                                       0.2s
 => [mermaid] resolving provenance for metadata file                                                               0.0s
/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:21535
  if (key == null || signature == null) throw new Error(`Cannot find matching keyid: ${JSON.stringify({ signatures, keys })}`);
                                              ^

Error: Cannot find matching keyid: {"signatures":[{"sig":"MEUCIQDjcCYqiW9XVgQbGcR/0JLibjbiPCU6O1v2Bx/UIV1kjQIgFmCUH5eATu0CRH0/ww0PwwMa8lycHaPyIvIxo2u004o=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"keys":[{"expires":null,"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","keytype":"ecdsa-sha2-nistp256","scheme":"ecdsa-sha2-nistp256","key":"MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE1Olb3zMAFFxXKHiIkQO5cJ3Yhl5i6UPp+IhuteBJbuHcA5UogKo0EWtlWwW6KSaKoTNEYL7JlCQiVnkhBktUgg=="}]}
    at verifySignature (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:21535:47)
    at fetchLatestStableVersion (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:21553:5)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async fetchLatestStableVersion2 (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:21672:14)
    at async Engine.getDefaultVersion (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22292:23)
    at async Engine.executePackageManagerRequest (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22390:47)
    at async Object.runMain (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:23096:5)

Node.js v22.12.0

I don't know if there is a workaround for this issue, but this wasn't mentioned in the docs, hence I am raising this issue.

Steps to reproduce

Just follow the steps in Documentation

Screenshots

No response

Code Sample

Setup

• Mermaid version: mermaid-js/tiny@11.13.0
• Browser and Version: [Chrome, Edge, Firefox] Edge

Suggested Solutions

Remove the 3.19@sha256:40dc4b415c17b85bea9be05314b4a753f45a4e1716bb31c01182e6c53d51a654 from the line FROM node:22.12.0-alpine3.19@sha256:40dc4b415c17b85bea9be05314b4a753f45a4e1716bb31c01182e6c53d51a654

But I am not sure what to do since the node image is explicitly set as immutable one

DISCLAIMER: This solution was suggested by AI.

Additional Context

No response

[lee-treehouse]

Previously I tried to get the project running in Docker, and encountered several errors including the one you've mentioned @klnsv

I didn't need Docker for my purposes but wanted to test that the change I made didn't break Docker.

I found that these were the issues:

• “Cannot find matching keyid” Error which can be resolved if we make minor bump to Node base image from node:22.12.0-alpine3.19 (will also need to update git version pinned in dockerfile)

• issues installing node-gyp, can be addressed by installing python in docker container.

I used a commit which addressed these issues a292399 to temporarily get the project working in Docker to assess the impact of my own changes.

If your goal is to unblock yourself, you could use that commit and roll it back before raising a PR.

Otherwise if someone is looking to fix this for the project, I suggest updating to latest Node 22 or ideally Node 24 for some longevity - see LTS calendar here

Regarding the node-gyp issue, if the only resolution is to install python in the container, for production I think it would be done a bit differently than in my commit, it's usually done with a two stage docker build, like described in this doc