[Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

This bug was fixed in the package lxc - 1.0.7-0ubuntu0.7 --- lxc (1.0.7-0ubuntu0.7) trusty-security; urgency=medium * REGRESSION FIX UPDATE: - Avoid /./ (LP: #1501491) -- Serge Hallyn Wed, 30 Sep 2015 15:41:40 -0500 ** Changed in: lxc (Ubuntu)

[Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

Hi I've just installed package from ppa: and I still have error below : lxc-start 1444041875.028 ERRORlxc_utils - utils.c:ensure_not_symlink:1407 - Mount onto /usr/lib/x86_64-linux-gnu/lxc//var/lock resulted in /run/lock, does not match root /usr/lib/x86_64-linux-gnu/lxc

Re: [Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

Hi, Can you show the results of dpkg -l | grep lxc sudo cat /var/lib/lxc//config sudo lxc-start -n -l trace -o /dev/stdout -F -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.

[Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

The Ubuntu Security Team has produced some packages built with the proposed fix from Serge (thanks again, Serge!). They have not been tested by the Security Team yet but those affected by this bug may find the packages useful. They can be found in: https://launchpad.net/~ubuntu-security-

[Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

Packages to address the issue in lxc are currently building in the ubuntu-security-proposed ppa: https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ ; please test these when they complete to verify that there aren't any additional regressions that have cropped up in this update.

[Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

I loaded the propsed fix on my system and both cases that failed before pass. No other issues seen. -- 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/1501491 Title: Unable to

Re: [Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

I loaded this on my system and both cases that failed before pass. No other issues seen. On Thu, Oct 1, 2015 at 3:15 AM Steve Beattie wrote: > Packages to address the issue in lxc are currently building in the > ubuntu-security-proposed ppa:

[Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

** Description changed: A partial fix was made for 1501310 - this case still fails. - /home/ubuntu/nzos/volumes/1.0.0/common/shared - /var/lib/lxc/0002/rootfs/nzos/./__shared__ none ro,bind 0 0 + /home/ubuntu//volumes/1.0.0/common/shared + /var/lib/lxc/0002/rootfs//./__shared__ none

[Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

** Tags added: patch -- 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/1501491 Title: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty Status in lxc

[Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

-- 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/1501491 Title: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty Status in lxc package in Ubuntu: New

[Touch-packages] [Bug 1501491] Re: Unable to start containers after upgrade to 1.0.7-0ubuntu0.6 on trusty

** Attachment added: "proposed debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1501491/+attachment/4480272/+files/debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu.