Open AlexisBRENON opened 1 week ago
I can't replicate this issue on my local machine using:
cat test-positive/flowchart1.mmd | docker run --rm -i ghcr.io/mermaid-js/mermaid-cli/mermaid-cli:11.2.1 --input - --output - --outputFormat svg
However, I have replicated this using GitHub Codespaces (which I believe uses similar machines to the default GitHub Actions runners), and I'm having the same issue. ghcr.io/mermaid-js/mermaid-cli/mermaid-cli:11.2.1
doesn't work, but ghcr.io/mermaid-js/mermaid-cli/mermaid-cli:11.2.1-beta.5
works.
Edit: Ah, I think I might know the issue. The -beta.x
Docker images are built using DockerfileBuild
, which uses Apline Linux 3.19:
However, the production Docker images are built using the Dockerfile
, which uses the latest version of Alpine Linux (currently 3.20): https://github.com/mermaid-js/mermaid-cli/blob/082fd7fbfcef41a8d968a895ea45b68dde75110a/Dockerfile#L1
However, it looks like version of Chromium in Apline Linux 3.20 doesn't play nicely with Puppeteer: https://github.com/puppeteer/puppeteer/issues/12637
I'm not 100% sure why we have both a Dockerfile
and a DockerfileBuild
, but I suspect just using the same one for everything should fix this issue.
Describe the bug With the newest versions of the docker image, I'm not able to render my chart anymore. The process hangs for a while and finally crash with the following error:
To Reproduce
Create a file
test.mmd
:Render the chart with old docker image:
Render the chart with new docker image:
Expected behavior I expected the rendering to succeed as previously.
Additional context You may see more examples in my repository which uses the image as part of the CI.