[MESOS-7225] Tasks launched via the default executor cannot access disk resource volumes.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Labels: mesosphere
• Target Version/s: 1.3.0
• Epic Link: pods-improvements
• Sprint: Mesosphere Sprint 52, Mesosphere Sprint 53
• Story Points: 3
• Assignee: Anand Mazumdar
• Reporter: Anand Mazumdar
• Shepherd: Vinod Kone
• Created: 09/Mar/17 17:37
• Updated: 23/Mar/17 20:03
• Resolved: 23/Mar/17 20:03

Description

Currently, when a task in a task group tries to access a volume specified in disk resources (e.g., persistent volumes), it doesn't have access to them since they are mounted in the root container (executor). This happens due to there being no mechanism to specify resources for child containers yet. Hence, by default any resources (e.g., disk) are added to the root container.

A possible solution can be to set up the mapping manually by the default executor using the SANDBOX_PATH volume source type giving child containers access to the volume mounted in the parent container. This is at best a workaround and the ideal solution would be tackled as part of MESOS-7207.