You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/02/09 00:58:00 UTC
[jira] [Commented] (MESOS-8534) Allow nested containers in
TaskGroups to have separate network namespaces
[ https://issues.apache.org/jira/browse/MESOS-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357777#comment-16357777 ]
ASF GitHub Bot commented on MESOS-8534:
---------------------------------------
GitHub user sagar8192 opened a pull request:
https://github.com/apache/mesos/pull/263
Allow nested containers in pods to have separate namespaces(Ref: MESOS-8534).
This change allows nested containers to have separate network and mount namespaces. It also retains the existing functionality, where a nested container can attach to parent's network and mount namespace.
I have not fixed/added tests for this. First, I want to make sure that this is the right approach. If this change looks good to the reviewers, I will fix/add unit tests.
After this change is shipped, the docs also need to be updated.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sagar8192/mesos sagarp-MESOS-MESOS-8534-allow-ip-per-container-in-pods
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/mesos/pull/263.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #263
----
commit 68deedb42212c42c6c7719e8432fd6b0031239c4
Author: Sagar Sadashiv Patwardhan <sa...@...>
Date: 2018-02-09T00:50:44Z
Allow nested containers in pods to have separate namespaces.
----
> 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)