[
https://issues.apache.org/jira/browse/MESOS-3599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976649#comment-14976649
]
Adam Avilla commented on MESOS-3599:
------------------------------------
[~ekesken] in your python example above you are having to do the loop
inspection to figure out where you need to docker logs / exec. Do you know if
anyone on mesos team is looking at exposing this just as an ENV var so that you
could potentially change to something like:
{code}
docker logs $DOCKER_PROCESS_NAME | grep 'Welcome to interaction-indexer.'
{code}
> COMMAND health checks with marathon running in slave context broken
> -------------------------------------------------------------------
>
> Key: MESOS-3599
> URL: https://issues.apache.org/jira/browse/MESOS-3599
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Erhan Kesken
> Assignee: haosdent
> Priority: Critical
>
> 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)
