[
https://issues.apache.org/jira/browse/MESOS-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370501#comment-16370501
]
Sagar Sadashiv Patwardhan commented on MESOS-8534:
--------------------------------------------------
[~alexr] We can document this behavior and add a check to validate that
HTTP/TCP is not set for nested containers that are requesting separate
namespaces(have NetworkInfos set in their ContainerInfo). If people are
interested in using HTTP health check, then we ask them to use command check
with `curl` instead, since both of them are equivalent. I will open a follow-up
ticket to fix HTTP and TCP health checks. We just need to find the PID of the
container and clone the health check process with namespaces of the target
nested container.
> 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 share
> namespaces with parent/root container.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
