[
https://issues.apache.org/jira/browse/MESOS-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15074220#comment-15074220
]
Zhitao Li commented on MESOS-3413:
----------------------------------
[~jieyu], thanks for the reply. My comment about symlink was indeed incorrect
and I updated my previous comment. I think returning the host path in the
resource offer could still work though, as long as Mesos slave would not change
the real location of the volume created.
For the fact of unable to update volumes for a running container is a
limitation, I acknowledge that's a limitation , but I don't really understand
why it's a show stopper. Making it clear to users that for DockerContainerizer,
all persistent volumes must be created and mounted before the
executor/container is created still sounds reasonable to me, and it allows us
to use current DockerContainerizer until the new Unified Containerizer is
available and covers other features we may need from docker engine.
One of the reasons I really want this is that our in-house database system
(which we are looking towards to run on Mesos) requires running multiple mysqld
instances on the same machine, and that team already spent quite some time to
dockerize these instances for easy configuration and isolation purpose.
Thanks for you time again. I really looking forward to using persistent volume
primitives!
> 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)
