Regression: Nested LXC is broken on Vivid

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

Just so it's clear, confirmed these steps are broken on an updated vivid install.

If both the host (vivid) and the outer guest run LXC from ppa:ubuntu-lxc/daily, the tested scenario works.

sudo add-apt-repository ppa:ubuntu-lxc/daily #on both the vivid host and at leas the outer guest (trusty).

N.b. Only works if both the host and the first guest run the ppa code - seems like only the host running the newest code doesn't help.

Ah, we have a new lxc and lxcfs currently stuck in vivid-proposed, I wonder if that'd include the fix you need.

Note that we're still working on fixing a bunch of regressions to allow those packages to migrate to vivid proper.

Oh, good to hear.

Can I easily test what's in vivid-proposed, and/or somehow influence the landing? Since I have a pretty good test set up for this particular scenario I might as well help you guys :)

You can temporarily turn on vivid-proposed in /etc/apt/sources.list.

lxcfs was released to vivid a couple of hours ago after the latest cgmanager landed fixing a test regressions due to systemd.

lxc is currently mostly held because of broken apparmor tests.

So, the new lxcfs in vivid-proposed does *not* solve this particular problem.

Again, running the daily PPA code solved this, but that means using the ppa for both vivid and trusty, not just vivid.

Don't hesitate to let me know how I can test more/further versions of LXC, including git branches, if needed.

This seems to be fixed in vivid with lxc 1.1.2:

tribaal@vivid-test:~$ apt-cache policy lxc
lxc:
  Installed: 1.1.2-0ubuntu1
  Candidate: 1.1.2-0ubuntu1
  Version table:
 *** 1.1.2-0ubuntu1 0
        500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
        100 /var/lib/dpkg/status

tribaal@vivid-test:~$ apt-cache policy lxc-templates
lxc-templates:
  Installed: 1.1.2-0ubuntu1
  Candidate: 1.1.2-0ubuntu1
  Version table:
 *** 1.1.2-0ubuntu1 0
        500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
        100 /var/lib/dpkg/status

Good to hear. We did have a bunch of fixes in there which were aimed at fixing that.

Ok, so it seems this isn't fixed after all.

Following the exact steps reported in my original message result in a non-starting container (same error message)

Adding ppa:ubuntu-lxc/daily seems to solve the problem.

I run into the same issue on a vivid host while trying to start a trusty nested container from inside a trusty container.

@Chris: Where do you add the ubuntu-lxc/daily ppa ? On the host or on the outer container ?

On the host.

Sorry for taking so long to answer, launchpad seems to have eaten my email answer...

Correction, on the host and on outer (just tried).

@Chris: Thanks !

I had to implement a different scheme not using nested containers but still requiring lxc-1.1.2.

I'll give nested containers another shot asap.

Hello Chris, or anyone else affected,

Accepted lxc into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Chris, or anyone else affected,

Accepted lxc into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.1.5-0ubuntu0.15.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

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 <email address hidden> Wed, 18 Nov 2015 13:41:23 -0500

The verification of the Stable Release Update for lxc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.