[
https://issues.apache.org/jira/browse/MESOS-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420267#comment-15420267
]
haosdent commented on MESOS-5961:
---------------------------------
For unified containerizer, we don't need to {{setns}} anymore. Because
mesos-executor executed in the container and have already entered the {{mnt}}
and {{net}} namespaces of the mesos container.
For docker containerizer, we only need to {{setns}} for {{net}} namespaces for
HTTP and TCP health check, for COMMAND health check, we wrap it via {{docker
exec}} to make sure our health check command enter the same namespaces of the
Docker container.
> HTTP and TCP health checks should support docker executor and bridged mode.
> ---------------------------------------------------------------------------
>
> Key: MESOS-5961
> URL: https://issues.apache.org/jira/browse/MESOS-5961
> Project: Mesos
> Issue Type: Improvement
> Reporter: Alexander Rukletsov
> Assignee: haosdent
> Labels: health-check, mesosphere
>
> If an executor and a task, e.g. the docker executor and docker container in
> bridged mode, exist in different network namespaces, HTTP and TCP health
> checks using {{localhost}} may not work properly. One solution would be to
> enter the container's network in the health check binary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
