[Docker] Use an absolute path for the entrypoint

Describe the bug

When using the docker image, specifying /data twice is a bit confusing:

docker run -it -v /path/to/diagrams:/data minlag/mermaid-cli -i /data/diagram.mmd

Expected behavior

The following syntax would be easier:

docker run -it -v `pwd`:/data minlag/mermaid-cli -i ./path/to/diagram.mmd

Solution

Define an absolute path for the entrypoint and set the workdir to /data

ADD puppeteer-config.json  /puppeteer-config.json
WORKDIR /data
ENTRYPOINT ["/home/mermaidcli/node_modules/.bin/mmdc", "-p", "/puppeteer-config.json"]

[daamien]

As a follow up, if the change breaks something, it will be fairly easy to restore the current behaviour with the --workdir option

docker run [...] --workdir=/home/mermaidcli minlag/mermaid-cli  -i /data/diagram.mmd -o /data/diagram.svg

[aloisklink]

The pandoc docker does it: https://github.com/pandoc/dockerfiles/blob/master/ubuntu/Dockerfile#L167

and you launch it like this

docker run  -v `pwd`:/data pandoc/latex foo.md

The point is to mount the current directory and use the docker image as binary command inside that directory

In that case, I’m open to changing the Dockerfile’s default WORKDIR, especially since as @MindaugasLaganeckas said, there’s a low chance of it breaking anything, and it definitely does make using the docker image easier! 😄