Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Porting Marathon Networking Doc to DC/OS #1066

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions 1.9/networking/service-and-pod-networking.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,8 @@ DC/OS services and pods declare `networks` the same way. Three modes of networki

In `host` networking, an application shares the network namespace of the Mesos agent process, typically the host network namespace.

**Note:** The `Network.name` parameter cannot be used with `host` networking.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so .. it's actually only useful for container mode. not host and not container/bridge.


## `container` Networking
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Container Networking without command syntax?


In container networking, an application should be allocated its own network namespace and IP address;
Expand Down