← Back to team overview

touch-packages team mailing list archive

[Bug 1436723] Re: Regression: Nested LXC is broken on Vivid

 

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3

---------------
lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
    - Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
    - Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.04.2) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
    - Fix ubuntu-cloud template to detect compression algorithm instead
      of hardcoding xz. Also update list of supported releases and use trusty
      as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
    meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.04.1) vivid-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
    (LP: #1497420, LP: #1436723, LP: #1441068, LP: #1504496,
     LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber <stgraber@xxxxxxxxxx>  Wed, 18 Nov 2015 13:41:23
-0500

** Changed in: lxc (Ubuntu Vivid)
       Status: Fix Committed => Fix Released

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

Title:
  Regression: Nested LXC is broken on Vivid

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released

Bug description:
  The nested LXC functionality seems to be broken on Vivid, at least
  with the following setup:

  Vivid (Host) -> Trusty (Outer LXC) -> Trusty (Inner LXC)

  What happens:

  The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/
  ( 631 cgroup error?  100 cgroups with this name already running seems to be the revelant error message).

  What is expected to happen:

  The inner LXC start command is expected to succeed and result in a
  running nested container.

  Steps to reproduce:

  - Install vivid server daily, update.
  - sudo apt-get install lxc
  - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER
  - sudo su
  - echo 'lxc.aa_profile = lxc-container-default-with-nesting' >> /var/lib/lxc/outer/config
  - exit
  - sudo lxc-start -n outer
  - (SSH to outer)
  - sudo apt-get update && sudo apt-get dist-upgrade
  - sudo apt-get install lxc
  - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER
  - sudo lxc-start -n inner

  Fails with: http://pastebin.ubuntu.com/10682639/
  Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/

  Control: The exact same scenario works on trusty and utopic. Tested by
  spinning up server installs (from isos) in KVMs and verifying
  manually.

  Any further log or information available on request, including KVM
  images demonstrating the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 26 08:43:56 2015
  InstallationDate: Installed on 2015-03-12 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  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/1436723/+subscriptions


References