Description
I forked the repository and cloned it locally to my Windows machine. Then I ran the
docker compose up --build -d mermaid
command to get a mermaid host to run in a docker container.
But this resulted in an error from the docker image:
2024-02-26 13:30:06 exec /mermaid/docker-entrypoint.sh: no such file or directory
Steps to reproduce
- Run `docker compose up --build -d mermaid'.
- Notice in Docker Desktop that the image has exited.
- Click the container name
mermaid-1 in Docker Desktop.
- Notice the error message in Logs window
Screenshots

Code Sample
No response
Setup
- Mermaid version: Latest develop version (10.2.4 according to package.json)
- Browser and Version: Chrome x64 122.0.6261.57
Suggested Solutions
If I start the mermaid image using the option --entrypoint=docker-entrypoint.sh, the container starts without error. So my suggestion is to change the Entrypoint reference in the docker-compose.yml file.
Additional Context
No response
Description
I forked the repository and cloned it locally to my Windows machine. Then I ran the
docker compose up --build -d mermaidcommand to get a mermaid host to run in a docker container.
But this resulted in an error from the docker image:
2024-02-26 13:30:06 exec /mermaid/docker-entrypoint.sh: no such file or directorySteps to reproduce
mermaid-1in Docker Desktop.Screenshots
Code Sample
No response
Setup
Suggested Solutions
If I start the mermaid image using the option
--entrypoint=docker-entrypoint.sh, the container starts without error. So my suggestion is to change the Entrypoint reference in the docker-compose.yml file.Additional Context
No response