[
https://issues.apache.org/jira/browse/MESOS-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906350#comment-14906350
]
Max Neunhöffer commented on MESOS-3413:
---------------------------------------
In understand all this and it works fine exactly like this for me.
My problem is the following: I do not know what path to take for "path1" (for
the set_host_path() method). When I make the persistent volume (call
makePersistent in the scheduler-API) I have to hand in the dynamically reserved
disk resource with a diskInfo that contains
a Volume. In there I *must not set* the host_path, otherwise I get an error
message. Then the makePersistent actually works, but I do not know where to get
the information which path the mesos agent picked for my persistent volume. If
I knew that path then I could do what you suggest, but I do not see any way to
learn that path!
This is my problem.
My comments about symlinks have probably been misleading, sorry for that.
> 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)
