Skip to content

Porting Marathon Networking Doc to DC/OS #1066

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.

Sign up for GitHub

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

Open
sascala wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Porting Marathon Networking Doc to DC/OS #1066

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
6b3ff85
Porting Marathon Networking Doc to DC/OS
May 19, 2017
adb8e0c
rename doc
May 19, 2017
95d430b
rename again
May 19, 2017
8dee1eb
moved important info in examples section higher in the doc
May 23, 2017
7935109
Update service-and-pod-networking.md
Aug 15, 2017
09554ed
Update service-and-pod-networking.md
Aug 15, 2017
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
5 changes: 4 additions & 1 deletion 1.9/networking/service-and-pod-networking.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,10 @@ When using the Docker containerizer, this translates to the Docker "default brid

@sascala sascala May 23, 2017

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I don't understand this part well enough to know if all of this is relevant for DC/OS users.

@jdef jdef Jul 11, 2017

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

yes, it's relevant. it used to be called docker BRIDGE mode networking. there was not previously a Mesos (UCR) equivalent, so it's new functionality for UCR consumers

Bridge mode networking allows you to map host ports to ports inside your containers. It is particularly useful if you are using a container image with fixed port assignments that you can't modify.

@joel-hamill joel-hamill Jul 12, 2017

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

With bridge mode networking, you can map host ports to ports inside your containers.


**Note:**: The UCR and Docker Containerizer support all network modes.
**Notes:**:

- The UCR and Docker Containerizer support all network modes.
- The `Network.name` parameter is only supported with `container` networking.

@jdef jdef Aug 15, 2017

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

👍


# Usage

Expand Down