[
https://issues.apache.org/jira/browse/MESOS-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742618#comment-14742618
]
Max Neunhöffer commented on MESOS-3413:
---------------------------------------
My comments about symlinks were probably wrong or at least misleading. I get
the sandbox allright in the docker container. However, I do not see any way so
far to get access from within the docker container to the persistent volume I
have previously allocated. I could add a volume (essentially leading to a -v in
the docker command line), if I only knew the path that the mesos slave intended
for me to use. I do set the container_path value but contrary to what you
indicate the persistent volume does not seem to be mounted in my docker
container. That is my real problem. Is there any documentation on this other
than the source code?
> 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
> Assignee: haosdent
> 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)
