Hi Having not received any answer, I support there is no solution for this.
The mesos slave process, along with accepting other docker arguments should somehow manage to take these extra arguments too. I have logged this as an enhancement, and wondering if somebody can look at this: https://issues.apache.org/jira/browse/MESOS-3187 I am available to provide the fix, if somebody can be a help as sheperd. Thx On 7/30/15, 12:58 PM, "Khanduja, Vaibhav" <[email protected]> wrote: >Hi > >jfyi, > >I have tried parameter option in marathon json file Š > >Š.. >"parameters": { > "key": "H", "value": "unix:///var/run/mydocker.sock" > } >Š. > > > > >On 7/30/15, 12:29 PM, "Khanduja, Vaibhav" <[email protected]> >wrote: > >>Hi >> >>I have a use-case where docker deamon does not run on original socket >>path which is /var/run/docker.sock but to a path as given by user. I >>start my docker daemon with H option, >> >>docker d H unix:///var/run/mydocker.sock >> >>all my docker calls now use this H for e.g. to print images: >> >>docker H unix:///var/run/mydocker.sock images >> >>I am using Marathon and have started my slave with Docker as container >>option. >> >>I cannot see an option in slave, where I can specify the socket port for >>the it talk with Docker daemon. docker_socket option is used for >>specifying docker port mapping in the container slave. >> >>Does this require code change in slave? >> >>Thx >
