[
https://issues.apache.org/jira/browse/MESOS-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946490#comment-14946490
]
Adam B commented on MESOS-3136:
-------------------------------
I can understand the desire to run in the docker, so that it has access to all
the environment/deps inside the container; or wanting to run it outside the
docker so you could query the docker engine itself. Perhaps only outside the
container is necessary, because the healthcheck command could specify to run
`docker exec whatever` if it wants to run something inside the container.
If we decide that this is an issue to pursue, let's please open a new JIRA
(clone this one, or otherwise link it), so we can track the new issue
separately from the one we've already shipped a "fix" for. Thanks!
> 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)
