[
https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946563#comment-14946563
]
Erhan Kesken commented on MESOS-3136:
-------------------------------------
as you stated, I think both option is required, at least at mesos-slave context
times we had a chance to apply a workaround to hold both options in our hands,
with an ugly line like this:
{noformat}
docker exec $(for i in $(docker ps -q --no-trunc); do docker inspect $i | grep
-sq MESOS_TASK_ID=${MESOS_TASK_ID:?} && echo $i; done) ls /
{noformat}
but now in docker context there is no workaround for getting other option. so I
see issue as a MUST.
> COMMAND health checks with Marathon 0.10.0 are broken
> -----------------------------------------------------
>
> Key: MESOS-3136
> URL: https://issues.apache.org/jira/browse/MESOS-3136
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Dr. Stefan Schimanski
> Assignee: haosdent
> Priority: Critical
> Fix For: 0.23.1, 0.24.1, 0.25.0
>
> Attachments: MESOS-3136_0_23_0.patch, MESOS-3136_0_24_0.patch
>
>
> When deploying Mesos 0.23rc4 with latest Marathon 0.10.0 RC3 command health
> check stop working. Rolling back to Mesos 0.22.1 fixes the problem.
> Containerizer is Docker.
> All packages are from official Mesosphere Ubuntu 14.04 sources.
> The issue must be analyzed further.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
