[
https://issues.apache.org/jira/browse/MESOS-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14732381#comment-14732381
]
Vaibhav Khanduja commented on MESOS-3376:
-----------------------------------------
Have you tried with this fix: https://issues.apache.org/jira/browse/MESOS-3187
> mess-slave is not respecting --docker_socket
> --------------------------------------------
>
> Key: MESOS-3376
> URL: https://issues.apache.org/jira/browse/MESOS-3376
> Project: Mesos
> Issue Type: Bug
> Components: docker
> Affects Versions: 0.23.0
> Reporter: Wojciech Sielski
> Priority: Minor
>
> Hi,
> I'm not sure if duplicate.
> We are staring mesos-slave inside container.
> Our default path for docker socket is /tmp/docker.sock
> so we start mess-slave like :
> {code}
> mesos-slave --master=zk://standalone:2181/mesos
> --containerizers=docker,mesos --executor_registration_timeout=5mins
> --hostname=standalone --ip=0.0.0.0 --docker_stop_timeout=5secs
> --gc_delay=1days --docker_socket=/tmp/docker.sock
> {code}
> unfortunately in stdeer I see:
> {code}
> I0906 09:37:30.637190 1041 exec.cpp:132] Version: 0.23.0
> I0906 09:37:30.641223 1042 exec.cpp:206] Executor registered on slave
> 20150906-092832-168470720-5050-376-S0
> Post
> http:///var/run/docker.sock/v1.20/containers/create?name=mesos-20150906-092832-168470720-5050-376-S0.191ef5b7-ad03-4fbf-b09b-5f5099d6fa6c:
> dial unix /var/run/docker.sock: no such file or directory.
> * Are you trying to connect to a TLS-enabled daemon without TLS?
> * Is your docker daemon up and running?
> W0906 09:37:30.641223 1041 logging.cpp:81] RAW: Received signal SIGTERM from
> process 531 of user 0; exiting
> {code}
> Seems like value is not propagated
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
