You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Anderson (JIRA)" <ji...@apache.org> on 2015/08/06 19:16:05 UTC

[jira] [Created] (MESOS-3219) Slave recovery issues with Docker containerizer

Benjamin Anderson created MESOS-3219:
----------------------------------------

             Summary: Slave recovery issues with Docker containerizer
                 Key: MESOS-3219
                 URL: https://issues.apache.org/jira/browse/MESOS-3219
             Project: Mesos
          Issue Type: Bug
            Reporter: Benjamin Anderson
            Priority: Minor


I'm working on setting up a Mesos environment with the
Docker containerizer and can't seem to get the recovery feature
working. I'm running CoreOS, so the slave processes themselves are
containerized. I have no issues running jobs without the recovery
features enabled, but all jobs fail to boot when I add the following
flags:

    MESOS_DOCKER_KILL_ORPHANS=false
    MESOS_DOCKER_MESOS_IMAGE=myrepo/my-slave-container

Inspecting the Docker images and their log output reveals that the
container invocation appears to be flawed - see this gist, which shows the arguments as retrieved via `docker inspect` as well as the failed container's log output:

https://gist.github.com/banjiewen/a2dc1784a82ed87edd6b

The containerizer is attempting to invoke an unquoted command via
`/bin/sh -c`, which, predictably, fails to pass the complete command.
This results in the error message shown in the second file in the
linked gist.

This is reproducible manually; quoting the arguments to `/bin/sh -c`
results in success (at least, it correctly receives the supplied
arguments).

The slave container itself is not logging anything of interest.

It's possible that my instance is configured incorrectly as well; the documentation here is a bit vague and there aren't many examples on the web.

I'm running Mesos 0.23.0 installed via http://repos.mesosphere.io/ in an Ubuntu 14.04 container. CoreOS is at the latest stable (717.3.0) which gives a Docker version at about 1.6.2.

I'm happy to provide more details if necessary. Cheers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)