-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
Docker daemon MTU not used when creating a new bridge network #34981
Comments
If I'm not mistaken, the I do see this is not being mentioned in the documentation (i.e., the "equivalent" does not mention that applies to the default bridge network), also we should update the dockerd flag descriptions for those flags that only apply to the default network. ping @mstanleyjones @mavenugo perhaps you're able to help pointing out which options only apply to the default bridge network |
@thaJeztah I'm ok with your remark but the problem is when you have an openstack environment, all networks should have a mtu=1450. |
I faced the same situation on openstack instance. |
👍 |
Have you reported an issue with the openstack maintainers? |
I think it's not an openstack problem. |
Auto-detecting MTU was removed at some point, because it would still be hit-and-miss, and cause issues in various situations; see #18108 |
Ok I understand the reasons but in this case, is it possible to add a parameter to configure by default all containers with a default MTU. Otherwise, we have to add it on each |
Yes, I wanna change MTU of NIC which is created and used by docker. |
We're running OpenStack(which is using VXLan) and we have to explicitly set the MTU for all overlay networks that are created. It would be useful to have an option to set the default MTU for all networks as right now using some else's compose file doesn't work without modifications. |
Hi @agxs , does ...
mtu: "1500",
... |
@mistyhacks that doesn't affect swarm networks. Sorry if I wasn't clear. |
That's surprising and I wonder if that is a bug. @aaronlehmann @stevvooe 🙏 |
@mistyhacks no, it's not a bug, the Custom networks and overlay networks can have a custom MTU defined on a per-network basis (through the |
@thaJeztah I understand but when you use Openstack (for example) you have to put a custom MTU for each network you want to create. So you have to update all docker-compose files.
|
I just realised that you can specify multiple compose files to a |
Maybe I'll try again. Can we set default configurations for network drivers when docker starts instead of asking the world to rewrite their recipe/compose file ? Astonishing the number of easy fixes to improve way of life that are simply ignored for multiple years. |
Would really love to see this feature! |
Description
I configure the
/etc/docker/daemon.json
with the "mtu" parameter to 1450.Default bridge is ok with mtu=1450.
But when a new bridge network is created (either
docker network create
ordocker-compose
), the mtu parameter is false. It's always 1500.Steps to reproduce the issue:
"mtu": 1450
to/etc/docker/daemon.json
docker network create my-net
Describe the results you received:
my-net MTU = 1500
Describe the results you expected:
my-net MTU = 1450
Output of
docker version
:Output of
docker info
:The text was updated successfully, but these errors were encountered: