[
https://issues.apache.org/jira/browse/MESOS-7513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014332#comment-16014332
]
Zhitao Li commented on MESOS-7513:
----------------------------------
An alternative is to simply add a {{sandbox_directory}} to the existing
{{GET_EXECUTORS}} call?
> Consider introducing an API call to get the sandbox of a running container.
> ---------------------------------------------------------------------------
>
> Key: MESOS-7513
> URL: https://issues.apache.org/jira/browse/MESOS-7513
> Project: Mesos
> Issue Type: Task
> Reporter: Anand Mazumdar
> Labels: mesosphere
>
> Currently, there is no public API for getting the path to the sandbox of a
> running container. This leads to folks reverse engineering the Mesos logic
> for generating the path and then using it in their scripts. This is already
> done by the Mesos Web UI and the DC/OS CLI. This is prone to errors if the
> Mesos path logic changes in the upcoming versions.
> We should introduce a new calls on the v1 Agent API;
> {{GET_CONTAINER_SANDBOX_PATH}}/{{GET_EXECUTOR_SANDBOX_PATH}} to get the path
> to a running container (can be nested) and another call to get the path to
> the executor sandbox.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
