You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jay Buffington (JIRA)" <ji...@apache.org> on 2014/08/21 15:02:10 UTC

[jira] [Resolved] (MESOS-1726) docker containerizer fails when container exits quickly

     [ https://issues.apache.org/jira/browse/MESOS-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Buffington resolved MESOS-1726.
-----------------------------------

    Resolution: Invalid

> docker containerizer fails when container exits quickly
> -------------------------------------------------------
>
>                 Key: MESOS-1726
>                 URL: https://issues.apache.org/jira/browse/MESOS-1726
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization
>            Reporter: Jay Buffington
>            Assignee: Timothy Chen
>              Labels: docker
>
> There is a race condition in the docker containerizer code that can usually be reproduced by running a command that exits quickly (for example, true) inside of a docker container.  You will see the error "Unable to get executor pid after launch” in the logs and the master will get a {{TASK_LOST}}.
> This race is between "docker inspect” and the process running inside the container.  When the processes inside the container exits (successful or not) before docker inspect runs docker inspect will return a Pid of 0.  When the pid is zero the {{Docker::Container::create}} method will set the pid to an empty {{Option<pid_t>}}.  This will cause the {{____launch}} method to return a {{Failure()}}.



--
This message was sent by Atlassian JIRA
(v6.2#6252)