[
https://issues.apache.org/jira/browse/MESOS-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072769#comment-15072769
]
Marc Villacorta commented on MESOS-2115:
----------------------------------------
Is there a way to define other volumes (or Docker parameters in general) to
bind-mount to the container where the executor is running (the one set by
_'docker_mesos_image'_)? I am trying to use:
{code:none}
--docker_mesos_image=mesosphere/mesos-slave:0.26.0-0.2.145.ubuntu1404
{code}
... but in CoreOS I must set some extra bind-mounts such as:
{code:none}
--volume /usr/bin/docker:/usr/bin/docker:ro
--volume /lib64/libdevmapper.so.1.02:/lib/libdevmapper.so.1.02:ro
--volume /lib64/libsystemd.so.0:/lib/libsystemd.so.0:ro
--volume /lib64/libgcrypt.so.20:/lib/libgcrypt.so.20:ro
{code}
Which Docker image do you set in _'--docker_mesos_image'_?
> Improve recovering Docker containers when slave is contained
> ------------------------------------------------------------
>
> Key: MESOS-2115
> URL: https://issues.apache.org/jira/browse/MESOS-2115
> Project: Mesos
> Issue Type: Epic
> Components: docker
> Reporter: Timothy Chen
> Assignee: Timothy Chen
> Labels: docker
> Fix For: 0.23.0
>
>
> Currently when docker containerizer is recovering it checks the checkpointed
> executor pids to recover which containers are still running, and remove the
> rest of the containers from docker ps that isn't recognized.
> This is problematic when the slave itself was in a docker container, as when
> the slave container dies all the forked processes are removed as well, so the
> checkpointed executor pids are no longer valid.
> We have to assume the docker containers might be still running even though
> the checkpointed executor pids are not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
