[openstack-dev] [Kuryr] Overlay MTU setup in docker remote driver

Liping Mao (limao) limao at cisco.com
Tue Aug 16 04:29:04 UTC 2016

Hi Kuryr team,

I just notice, this can be fixed in kuryr bind code.
I submit a bug to track this:

And patch sets are here:


Liping Mao

On 16/8/15 下午11:20, "Liping Mao (limao)" <limao at cisco.com> wrote:

>Hi Kuryr team,
>I open an issue in docker-libnetwork:
>Appreciate for any idea or comments. Thanks.
>Liping Mao
>On 16/8/12 下午4:08, "Liping Mao (limao)" <limao at cisco.com> wrote:
>>Hi Kuryr team,
>>When the network in neutron using overlay for vm,
>>it will use dhcp option to control the VM interface MTU,
>>but for docker, the ip address does not get from dhcp.
>>So it will not set up proper MTU in container.
>>Two work-around in my mind now:
>>1. Set the default MTU in docker to 1450 or less.
>>2. Manually configure MTU after container start up.
>>But both of these are not good, the idea way in my mind
>>is when libnetwork Call remote driver create network,
>>kuryr create neutron network, then return Proper MTU to libnetwork,
>>docker use this MTU for this network. But docker remote driver
>>does not support this.
>>Or maybe let user config MTU in remote driver,
>>a little similar with overlay driver:
>>But now, seems like remote driver will not do similar things.
>>Any idea to solve this problem? Thanks.
>>Liping Mao
>>OpenStack Development Mailing List (not for usage questions)
>>OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

More information about the OpenStack-dev mailing list