[MESOS-3413] Docker containerizer does not symlink persistent volumes into sandbox

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.0
• Fix Version/s: 0.28.0
• Component/s: agent, containerization, docker
• Labels: docker mesosphere persistent-volumes
• Flags: Important
• Epic Link: Persistence
• Sprint: Mesosphere Sprint 28, Mesosphere Sprint 29
• Story Points: 5
• Assignee: Timothy Chen
• Reporter: Max Neunhöffer
• Shepherd: Jie Yu
• Created: 11/Sep/15 14:06
• Updated: 26/Nov/18 12:53
• Resolved: 26/Nov/18 12:53

Description

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.

Issue Links

• relates to: MESOS-2840 MesosContainerizer support multiple image provisioners