oneiric container install problem: resolvconf

Thanks for taking the time to report this bug.

Unfortunately I can't reproduce it. Can you show exactly what command you used to create the container, the contents of the configuration file passed (i.e. -f lxc.conf), and how your network is set up?

commands:

sudo rm -fr /var/cache/lxc/oneiric
sudo lxc-create -t ubuntu -n test -f /etc/lxc/local.conf -- -r oneiric -a i386

errors during creation are shown only when container cache is bootstrapped (but the problem is still there also when the cache is just copied)

in the host:

cat /etc/network/interfaces

# The loopback network interface
auto lo
iface lo inet loopback

auto br0
iface br0 inet dhcp
bridge_ports eth0

cat /etc/lxc/local.conf

lxc.network.type=veth
lxc.network.link=br0
lxc.network.flags=up
lxc.arch=i686

resolvconf is not insatalled in the host either (as per default) as currently does not behave as expected

in the container:

cat /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

if I remove resolvconf from oneiric extra packages in /usr/lib/lxc/templates/lxc-ubuntu everything works properly.

Actually it seems that inetutils-ping is the problem.

   packages=inetutils-ping
   debootstrap --verbose --components=main,universe --include=$packages oneiric o

has the problem, but

   packages=resolvconf
  debootstrap --verbose --components=main,universe --include=$packages oneiric o

does not.

Ok, there are two bugs here.

inetutils-ping causes the warning lines:

W: Failure while installing base packages. This will be re-attempted up to five times.

resolvconf causes resolv.conf to be empty until you do 'ifdown eth0; ifup eth0'.

I will pull resolvconf from the template. I don't think it's worth pulling inetutils-ping from the package list to quiet that warning. (Please feel free to pursuade me if you disagree)

Note the resolvconf bug does not affect natty.

I do agree. It's the same solution I adopted locally ;)

This bug was fixed in the package lxc - 0.7.5-0ubuntu10

---------------
lxc (0.7.5-0ubuntu10) precise; urgency=low

  * debian/patches/0009-ubuntu-template-drop-resolvconf.patch:
    Drop resolvconf from package list for oneiric containers. It appears
    to stop containers from getting a useful resolv.conf without doing
    ifdown; ifup; and is apparently unwanted anyway. (LP: #880020)
  * debian/lxcguest.lxcguest.upstart: mkdir /run/lock on boot
    (LP: #880030)
  * debian/fstab.lxc and debian/fstab.libvirt: mount tmpfs on /run/lock,
    not /var/lock (as per new stock /lib/init/fstab).
 -- Serge Hallyn <email address hidden> Mon, 24 Oct 2011 11:45:53 -0500

Hello xlyz, or anyone else affected,

Accepted lxc into oneiric-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tested and works as expected.

Status changed to 'Confirmed' because the bug affects multiple users.

This bug was fixed in the package lxc - 0.7.5-0ubuntu8.2

---------------
lxc (0.7.5-0ubuntu8.2) oneiric-proposed; urgency=low

  * debian/patches/0009-ubuntu-template-drop-resolvconf.patch:
    Drop resolvconf from package list for oneiric containers. It appears
    to stop containers from getting a useful resolv.conf without doing
    ifdown; ifup; and is apparently unwanted anyway. (LP: #880020)
  * debian/lxcguest.lxcguest.upstart: mkdir /run/lock on boot
    (LP: #880030)
  * debian/fstab.lxc and debian/fstab.libvirt: mount tmpfs on /run/lock,
    not /var/lock (as per new stock /lib/init/fstab).
 -- Serge Hallyn <email address hidden> Wed, 02 Nov 2011 22:49:42 +0000

oneiric has seen the end of its life and is no longer receiving any updates. Marking the oneiric task for this ticket as "Won't Fix".