Skip to content

Clarify the mtu option is supported by overlay driver #451

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

Merged
merged 1 commit into from
Nov 4, 2016
Merged

Clarify the mtu option is supported by overlay driver #451

merged 1 commit into from
Nov 4, 2016

Conversation

aboch
Copy link
Contributor

@aboch aboch commented Nov 3, 2016

No description provided.

@@ -160,6 +160,8 @@ equivalent docker daemon flags used for docker0 bridge:
| `com.docker.network.bridge.host_binding_ipv4` | `--ip` | Default IP when binding container ports |
| `com.docker.network.driver.mtu` | `--mtu` | Set the containers network MTU |

The `com.docker.network.driver.mtu` option is also supported by the `overlay` driver.

Choose a reason for hiding this comment

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

Thanks for the PR. This file is not maintained in docker.github.io repo and needs to be changed in docker/docker instead. Please remove it from this PR and open another one in that repo. You can link that PR to this one for tracking purposes.

The other file is fine for this PR.

@aboch
Copy link
Contributor Author

aboch commented Nov 4, 2016

Thanks @mstanleyjones. I updated the PR.
The docker/docker dommandline reference change is part of moby/moby#26880

@mdlinville mdlinville merged commit 66a183b into docker:master Nov 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants