You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This question is about expected behavior of the "extra command line arguments" provided to this endpoint:
POST /api/requests/request/{requestId}/run
Are these extra command line args ignored when using the default Mesos executor? When I provide extra args they appear in the JSON/UI for the task, but I don't see them being appended to the command and aren't in the stdout or stderr logs.
For example, if I create an on-demand request and deploy it with the command "echo" and provide the extra arg "hello world", I expect to see "hello world" appended to the command in stdout ("echo hello world") and also printed to stdout as a result; this does not happen (but I see the extra args in the JSON/UI). It DOES behave as I expect when using a custom executor type with /usr/local/bin/singularity-executor, and I'm confused why there's a difference in behavior there. It seems like the API (and UI) should prevent extra command line args when using the default Mesos executor, but maybe I just don't get what's going on or how it's intended to work!
I observed this behavior in Singularity 0.4.7 and 0.4.11 (in a local dev setup using docker and docker-compose per the instructions, checking out the relevant git tags).
The text was updated successfully, but these errors were encountered:
Interesting, I was able to reproduce this locally as well. I see the extra args showing up in the arguments field for the mesos task info, but I am seeing the same as you for the actually output. I'll look into how the arguments field is treated in the default executor and see what's up. Thanks for reporting this.
This question is about expected behavior of the "extra command line arguments" provided to this endpoint:
POST /api/requests/request/{requestId}/run
Are these extra command line args ignored when using the default Mesos executor? When I provide extra args they appear in the JSON/UI for the task, but I don't see them being appended to the command and aren't in the stdout or stderr logs.
For example, if I create an on-demand request and deploy it with the command "echo" and provide the extra arg "hello world", I expect to see "hello world" appended to the command in stdout ("echo hello world") and also printed to stdout as a result; this does not happen (but I see the extra args in the JSON/UI). It DOES behave as I expect when using a custom executor type with /usr/local/bin/singularity-executor, and I'm confused why there's a difference in behavior there. It seems like the API (and UI) should prevent extra command line args when using the default Mesos executor, but maybe I just don't get what's going on or how it's intended to work!
I observed this behavior in Singularity 0.4.7 and 0.4.11 (in a local dev setup using docker and docker-compose per the instructions, checking out the relevant git tags).
The text was updated successfully, but these errors were encountered: