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

docker compose up ignored the daemon mtu value #3438

Closed
cristinelvasluianu opened this issue May 10, 2016 · 1 comment
Closed

docker compose up ignored the daemon mtu value #3438

cristinelvasluianu opened this issue May 10, 2016 · 1 comment

Comments

@cristinelvasluianu
Copy link

@cristinelvasluianu cristinelvasluianu commented May 10, 2016

When we are using docker compose to launch a docker container, the container will always have the default value for mtu size (1500), even when we start the docker daemon with a custom size (Eg: docker daemon --mtu=1460).

Steps to reproduce

  1. Start docker daemon using a custom mtu size
    docker daemon --mtu=1460
  2. Launch a container using docker compose
    docker-compose.yml:
    version: '2'
    services:
    db:
    image: postgres
  3. Check the mtu size of eth0 interface for the launched container
  • login into container: docker exec -it containerName bash
  • cmd: ifconfig

Expected result:

  • The MTU size for the launched container should be equal with daemon mtu option (in our case 1460 bytes)

Actual result:

  • The MTU size for the launched container have the default mtu value 1500 bytes

NOTE
docker-compose info
docker-compose version 1.6.2, build 4d72027
docker-py version: 1.7.2
CPython version: 2.7.5
OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013

docker info
Client:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Wed Apr 27 00:34:42 2016
OS/Arch: linux/amd64

Server:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Wed Apr 27 00:34:42 2016
OS/Arch: linux/amd64

system info
Linux weave-machine 3.10.0-327.13.1.el7.x86_64 #1 SMP Thu Mar 31 16:04:38 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

@rbclark

This comment has been minimized.

Copy link

@rbclark rbclark commented Oct 3, 2016

Just wondering why this was closed? I see there was an issue opened for a similar issue with regular docker and someone mentioned a workaround moby/moby#22297 (comment) but it definitely doesn't seem like an actual solution and more of a workaround. It also doesn't work very well if you are trying to move between different environments with different MTU's.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.