mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhitao Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-3413) Docker containerizer does not symlink persistent volumes into sandbox
Date Fri, 25 Dec 2015 05:53:49 GMT

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

Zhitao Li commented on MESOS-3413:
----------------------------------

It seem that this task is marked as "Won't fix". I wonder whether it's possible to come up
with some short fix for the existing docker containerizer so users don't need to blocked until
new Unified Containerizer is ready.

There seem to be two possible "quick" fixes:
- symlink the persistent volume into sandbox;
- directly mount the persistent volume.

The getPersistentVolumePath() in src/slave/paths.cpp is already available for this purpose.

Can someone comment on this possibility?

> 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)

Mime
View raw message