would allow to directly interact with the mwsd binary:
docker run mathwebsearch to run mwsd on port 8080 with the harvest in /data (like at the moment)
docker run mathwebsearch --help to run mwsd --help
docker run mathwebsearch -p 8888 -I /myData to run mwsd on port 8888 with the harvest in /myData
(Not sure if the CMD part should also be moved to the ENTRYPOINT as defaults - probably depends on the implementation. That is, how does it handle two -p and -I options?)
Splitting the CMD in the Dockerfile into an ENTRYPOINT and CMD would give an more intuitive CLI. For example, this Dockerfile:
would allow to directly interact with the
mwsdbinary:docker run mathwebsearchto runmwsdon port 8080 with the harvest in/data(like at the moment)docker run mathwebsearch --helpto runmwsd --helpdocker run mathwebsearch -p 8888 -I /myDatato runmwsdon port 8888 with the harvest in/myData(Not sure if the CMD part should also be moved to the ENTRYPOINT as defaults - probably depends on the implementation. That is, how does it handle two
-pand-Ioptions?)For a more detailed explanation, see https://stackoverflow.com/questions/21553353/what-is-the-difference-between-cmd-and-entrypoint-in-a-dockerfile