When I've setup a docker ON_DEMAND job and tried passing in args from the UI, I see that the command line input is not split on whitespace. Here's the relevant bits of doing a docker inspect after the fact on a container that was launched by singularity in this way:
$ sudo docker inspect 54f8c357cd4f
[
{
"Id": "54f8c357cd4fa214fefae11bbf27ab3b5851c49861f2fa3fb280ed716100d613",
"Created": "2016-03-11T19:34:39.312828156Z",
"Path": "/usr/bin/node",
"Args": [
"/app/lib/echo.js hi"
],
The command line I passed in the UI was: /app/lib/echo.js hi. the --entrypoint I specified for the container was /usr/bin/node. What I was hoping for was that the command line input I specified in the singularity UI would be passed as separate args (split on whitespace). It seems like the optional command line input you specify in the UI should either a) split that input on whitespace or b) the UI should allow you to specify multiple arguments (one textfield for each).
fwiw - There is a similar (multiple textfields) capability over in the ENV var setup for new container deploys.
When I've setup a docker ON_DEMAND job and tried passing in args from the UI, I see that the command line input is not split on whitespace. Here's the relevant bits of doing a
docker inspectafter the fact on a container that was launched by singularity in this way:The command line I passed in the UI was:
/app/lib/echo.js hi. the --entrypoint I specified for the container was/usr/bin/node. What I was hoping for was that the command line input I specified in the singularity UI would be passed as separate args (split on whitespace). It seems like the optional command line input you specify in the UI should either a) split that input on whitespace or b) the UI should allow you to specify multiple arguments (one textfield for each).fwiw - There is a similar (multiple textfields) capability over in the ENV var setup for new container deploys.