args for Docker run surrounded by quotes

2014-10-29 Thread Andrew Jones
Hi, I'm trying to run a Docker image which has a defined entrypoint and pass args to it. It looks like when the args are passed to docker run, they are surrounded by single quotes. The image I am trying to run is tomaskral/chronos, and this is the configuration I am giving to Marathon: { "id":

Re: args for Docker run surrounded by quotes

2014-10-29 Thread Timothy Chen
Hi Andrew, By default shell is enabled, which wraps your command in bin/sh and single quotes. Try passing shell false to marathon. Tim Sent from my iPhone > On Oct 29, 2014, at 4:44 AM, Andrew Jones > wrote: > > Hi, > > I'm trying to run a Docker image which has a defined entrypoint and p

Re: args for Docker run surrounded by quotes

2014-10-29 Thread Andrew Jones
Thanks a lot TIm. That worked perfectly. Thanks, Andrew On Wed, Oct 29, 2014, at 03:58 PM, Timothy Chen wrote: > Hi Andrew, > > By default shell is enabled, which wraps your command in bin/sh and > single quotes. > > Try passing shell false to marathon. > > Tim > > Sent from my iPhone > > >

Re: args for Docker run surrounded by quotes

2014-10-29 Thread Connor Doyle
Andrew, could you explain what you changed to make this work? Marathon doesn't expose a `shell` argument; it's set implicitly by using either `cmd` or `args` in the app JSON. `args` is what you want (sets shell to false) if you are using a Dockerfile with an ENTRYPOINT clause. `args` is an arr

Re: args for Docker run surrounded by quotes

2014-10-30 Thread Andrew Jones
When I tried passing arguments as an array yesterday I got this output from Chronos: + logged chronos run_jar '--master zk://...:2181/mesos' '--zk_hosts zk://...:2181' So more quotes. Then I added `shell: false` and it worked, so I thought that fixed it. However, today if I destroy Chronos and r