I did try removing the /proc and adding just pid=host but still no dice with that. Need to have a deeper dig into the docker 1.9 changelog. Will post back if I find anything.
Thanks, Graham. On 31 Dec 2015, at 20:27, Tim Chen <t...@mesosphere.io<mailto:t...@mesosphere.io>> wrote: I don't think you need to mount in /proc if you have --pid=host already, can you try that? Tim On Thu, Dec 31, 2015 at 4:16 AM, Taylor, Graham <graham.x.tay...@capgemini.com<mailto:graham.x.tay...@capgemini.com>> wrote: Hey folks, I’m trying to get Mesos slave up and running in a docker container on CoreOS. I’ve successfully got the master up and running but anytime I start the slave container I receive the following error - Failed to create a containerizer: Could not create DockerContainerizer: Failed to create docker: Failed to get docker version: Failed to execute 'docker -H unix:///var/run/docker.sock --version': exited with status 127 I’m starting the slave container with the following command - /usr/bin/docker run --rm --name mesos_slave \ --net=host \ --privileged \ --pid=host \ -p 5051:5051 \ -v /sys:/sys \ -v /proc:/host/proc:ro \ -v /usr/bin/docker:/usr/bin/docker:ro \ -v /var/run/docker.sock:/var/run/docker.sock \ -v /lib64/libdevmapper.so.1.02:/lib/libdevmapper.so.1.02:ro \ -e "MESOS_MASTER=zk://172.31.1.11:2181<http://172.31.1.11:2181>,172.31.1.12:2181<http://172.31.1.12:2181>,172.31.1.13:2181/mesos<http://172.31.1.13:2181/mesos>" \ -e "MESOS_EXECUTOR_REGISTRATION_TIMEOUT=10mins" \ -e "MESOS_CONTAINERIZERS=docker" \ -e "MESOS_RESOURCES=ports(*):[31000-32000]" \ -e "MESOS_IP=172.31.1.14" \ -e "MESOS_WORK_DIR=/tmp/mesos" \ -e "MESOS_HOSTNAME=172.31.1.14" \ mesosphere/mesos-slave:0.25.0-0.2.70.ubuntu1404 I’ve also tried with various other versions of the Docker image (including 0.26.0) but I keep receiving the same error. I’m running on CoreOS beta channel (877.1.0) which has docker installed and the service running - docker --version Docker version 1.9.1, build 4419fdb-dirty If I change the /proc mount to be /proc:/proc I get past the docker version error but receive a different error - Error response from daemon: Cannot start container 51a9b60f702a0f13f975fd2e7f4b642180d5363565e042702665098e8761b758: [8] System error: "/var/lib/docker/overlay/51a9b60f702a0f13f975fd2e7f4b642180d5363565e042702665098e8761b758/merged/proc" cannot be mounted because it is located inside "/proc” I had a search on the wiki and found some similar related issues https://issues.apache.org/jira/browse/MESOS-3498?jql=project%20%3D%20MESOS%20AND%20text%20~%20%22Failed%20to%20execute%20%27docker%20version%22 but they all seem to be closed/resolved/won’t fix. Is anyone successfully running a slave on CoreOS and can help me fix up my Docker command? Thanks, Graham. ________________________________ Capgemini is a trading name used by the Capgemini Group of companies which includes Capgemini UK plc, a company registered in England and Wales (number 943935) whose registered office is at No. 1, Forge End, Woking, Surrey, GU21 6DB. ________________________________ Capgemini is a trading name used by the Capgemini Group of companies which includes Capgemini UK plc, a company registered in England and Wales (number 943935) whose registered office is at No. 1, Forge End, Woking, Surrey, GU21 6DB.
