touch-packages team mailing list archive

[Serge Hallyn <1355813@xxxxxxxxxxxxxxxxxx>]

Hi James,

does setting lxc.network.mtu = 9000 in the container configuration file
work?

Depending on how juju creates the containers, you may be able to simply
add that line to the bottom of /etc/lxc/default.conf to get the desired
result.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1355813

Title:
  LXC containers reset bridge MTU on start/restart

Status in juju-core:
  New
Status in MAAS:
  New
Status in “lxc” package in Ubuntu:
  New

Bug description:
  Context:

  juju + MAAS deployed OpenStack environment, misc services deployed
  under LXC on the bootstrap node, interfaces configured for jumbo
  frames - note that I had to manually set the LXC container interfaces
  to mtu 9000 before the bridge would do the same.

  Action:

  Reboot one of the containers; MTU on br0 resets from 9000 -> 1500.

  This feels like more of a 'we need a better way to orchestrate MTU
  configuration across different services' so raising tasks for MAAS and
  Juju as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.5-0ubuntu0.1
  ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Tue Aug 12 13:26:00 2014
  KernLog:

  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxcsyslog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions