touch-packages team mailing list archive

[Serge Hallyn <1367495@xxxxxxxxxxxxxxxxxx>]

Actually I was thinking this was bug 1240757.

@zukoff-f:  your comment #25 would be more appropriate there.  That's
where we should discuss how to have bind9, dnsmasq, and lxc cooperate.

This bug seems to have evidence from several different causes.
yoniyo0's was a bad lxc-usernet file.  I'm not sure what Dan Kegel's
actually was.  I'm going to mark this bug invalid for lxc and not
affecting bind9 as I don't know that we can sanely identify the actual
original problem..

As for bug 1240757, perhaps our stock bind9 packaging should simply
exclude anything begging with 'lxc', or only lxcbr0 (since users may
define a lxcbr2 and want bind9 to listen on it)


** No longer affects: bind9 (Ubuntu)

** Changed in: lxc (Ubuntu)
       Status: Triaged => Invalid

-- 
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/1367495

Title:
  Bridge still not created if bind9 is on

Status in lxc package in Ubuntu:
  Invalid

Bug description:
  This is probably a dup of bug 1240757, created just so I could upload
  the data requested in that bug report.

  On a fresh, probably vanilla, ubuntu 14.04 server, I tried using ubuntu 14.04's default lxc.
  It created containers fine, but they failed to start, complaining
    lxc-start: failed to attach 'veth9HNUS9' to the bridge 'lxcbr0' : No such device
  /var/log/upstart/lxc-net.log says
    dnsmasq: failed to create listening socket for 10.0.3.1: Address already in use

  This didn't happen on a desktop 14.04 instance, where bind9 is not
  installed by default.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Tue Sep  9 16:39:34 2014
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1367495/+subscriptions