[jira] [Comment Edited] (MESOS-3413) Docker containerizer does not symlink persistent volumes into sandbox

["Vaibhav Khanduja (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741150#comment-14741150 ] 

Vaibhav Khanduja edited comment on MESOS-3413 at 9/11/15 5:12 PM:
------------------------------------------------------------------

I see the code for docker.cpp it is mapping sandbox directory as volumes inside the container. The value of the sandbox directory is coming in as environment variables:"MESOS_SANDBOX"
......
 argv.push_back("-e");
 argv.push_back("MESOS_SANDBOX=" + mappedDirectory);
 argv.push_back("-e");
 argv.push_back("MESOS_CONTAINER_NAME=" + name);
.......

May be good idea to try this for now, though not a good solution ... 

Docker bind mounts these volumes inside container ... a symlink to a directory would be mounted but since it does chroot, the link may not be valid inside the container .... 


was (Author: vaibhavkhanduja):
I see the code for docker.cpp it is mapping sandbox directory as volumes inside the container. The value of the sandbox directory is coming in as environment variables:"MESOS_SANDBOX"
......
 argv.push_back("-e");
 argv.push_back("MESOS_SANDBOX=" + mappedDirectory);
 argv.push_back("-e");
 argv.push_back("MESOS_CONTAINER_NAME=" + name);
.......

May be good idea to try this for now, though not a good solution ... 

> Docker containerizer does not symlink persistent volumes into sandbox
> ---------------------------------------------------------------------
>
>                 Key: MESOS-3413
>                 URL: https://issues.apache.org/jira/browse/MESOS-3413
>             Project: Mesos
>          Issue Type: Bug
>          Components: containerization, docker, slave
>    Affects Versions: 0.23.0
>            Reporter: Max Neunhöffer
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> For the ArangoDB framework I am trying to use the persistent primitives. nearly all is working, but I am missing a crucial piece at the end: I have successfully created a persistent disk resource and have set the persistence and volume information in the DiskInfo message. However, I do not see any way to find out what directory on the host the mesos slave has reserved for us. I know it is ${MESOS_SLAVE_WORKDIR}/volumes/roles/<myRole>/<NAME>_<UUID> but we have no way to query this information anywhere. The docker containerizer does not automatically mount this directory into our docker container, or symlinks it into our sandbox. Therefore, I have essentially no access to it. Note that the mesos containerizer (which I cannot use for other reasons) seems to create a symlink in the sandbox to the actual path for the persistent volume. With that, I could mount the volume into our docker container and all would be well.



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