[
https://issues.apache.org/jira/browse/MESOS-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366490#comment-16366490
]
Sagar Sadashiv Patwardhan commented on MESOS-8534:
--------------------------------------------------
I discussed this with [~jieyu] today. Making TCP and HTTP healthchecks work is
not straightforward and will require a lot of work. He suggested that we can
use command check instead. Command check for nested containers already executes
commands under the target nested container namespaces. So, we can use this
`curl 127.0.0.1:<port>` instead of HTTP healthcheck. This solution works for
our use case.
> Allow nested containers in TaskGroups to have separate network namespaces
> -------------------------------------------------------------------------
>
> Key: MESOS-8534
> URL: https://issues.apache.org/jira/browse/MESOS-8534
> Project: Mesos
> Issue Type: Task
> Components: containerization
> Reporter: Sagar Sadashiv Patwardhan
> Priority: Minor
> Labels: cni
>
> As per the discussion with [~jieyu] and [~avinash.mesos] , I am going to
> allow nested containers in TaskGroups to have separate namespaces. I am also
> going to retain the existing functionality, where nested containers can
> connect to parent/root containers namespace.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
