Unable to start LXC Container

[Royston Carter]

Binary package hint: lxc

root@vmserver:/# lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04

I have a problem starting LXC Containers on an AMD64 Lucid installation. This issue appears very similar to bug #566827 though my conditions are not as described in that bug. I have a single debian container that had been running flawlessly for some weeks. The container was started and stopped a number of times and always started successfully. My /var is not a separately mounted file system. Following an unplanned power off of the system (I have spoken to the wife and this will not happen again) I now get the following as reported in #566827.

lxc-start: Device or resource busy - could not unmount old rootfs
lxc-start: failed to pivot_root to '/home/rpcarter/lxc/MusicServ01/rootfs'
lxc-start: failed to set rootfs for 'MusicServ01'
lxc-start: failed to setup the container

I have made no changes to the system but automatic updates would have occurred. I have destroyed and recreated the container and also build a new one with lxc-debian from scratch but this error is consistently there.

If the solution is as described in #566827 and little more clarity on how this is applied would be appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: lxc 0.6.5-1
ProcVersionSignature: Ubuntu 2.6.32-25.44-server 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-server x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Mon Oct 4 14:22:45 2010
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: lxc

[Daniel Lezcano (daniel-lezcano)]

This bug was fixed in the next release of lxc.

The commit fixing this problem is:
http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commit;h=c08556c6ece8ad8308f7636adb0ad25b60e3a16d

Does it makes sense to take the lxc-0.7.2 version for lucid ? As it is compatible for the kernel ?

[Royston Carter (rpcarter)]

  Daniel,
     Firstly is it likely that this will come out shortly as a patch to
Lucid? If so and in a matter of days rather than weeks then I will wait.
Alternatively could you point me at documentation that would explain how
I apply the fix from the git repository you allude to in you email.

Regards

Roy.

On 07/10/2010 22:09, Daniel Lezcano wrote:
> This bug was fixed in the next release of lxc.
>
> The commit fixing this problem is:
> http://lxc.git.sourceforge.net/git/gitweb.cgi?p=lxc/lxc;a=commit;h=c08556c6ece8ad8308f7636adb0ad25b60e3a16d
>
> Does it makes sense to take the lxc-0.7.2 version for lucid ? As it is
> compatible for the kernel ?
>

[Daniel Lezcano (daniel-lezcano)]

On 10/08/2010 12:56 AM, Royston Carter wrote:
> Daniel,
> Firstly is it likely that this will come out shortly as a patch to
> Lucid? If so and in a matter of days rather than weeks then I will wait.
>

The patch in attachment is a fix for this problem.
If the package maintainer is willing to merge it that will be great.

> Alternatively could you point me at documentation that would explain how
> I apply the fix from the git repository you allude to in you email.
>

The simpler is:

     * install the quilt tools
     * save the patch in attachment
     * cd <lxc-topmost-dir>
     * quilt import <path-to-patch>/0001-use-lazy-...
     * quilt push

Then the usual configure, make, etc ...

Let me know if that fixes your problem

Thanks
      -- Daniel

[Royston Carter (rpcarter)]

  Daniel,
     Can we step back a little here please. I have never to date amended
or patched a Linux component/application so could do with your second
step explaining. You say "* cd <lxc-topmost-dir> " but does this assume
I have lxc source installed? If this is required could you add a line
for how I get this.

  Thanks for you response to this.

Regards

Roy

On 08/10/2010 10:53, Daniel Lezcano wrote:
> On 10/08/2010 12:56 AM, Royston Carter wrote:
>> Daniel,
>> Firstly is it likely that this will come out shortly as a patch to
>> Lucid? If so and in a matter of days rather than weeks then I will wait.
>>
> The patch in attachment is a fix for this problem.
> If the package maintainer is willing to merge it that will be great.
>
>> Alternatively could you point me at documentation that would explain how
>> I apply the fix from the git repository you allude to in you email.
>>
> The simpler is:
>
> * install the quilt tools
> * save the patch in attachment
> * cd<lxc-topmost-dir>
> * quilt import<path-to-patch>/0001-use-lazy-...
> * quilt push
>
> Then the usual configure, make, etc ...
>
> Let me know if that fixes your problem
>
> Thanks
> -- Daniel
>
>
> ** Patch added: "0001-use-lazy-umount-when-umount-returns-EBUSY.patch"
> https://bugs.launchpad.net/bugs/654552/+attachment/1678598/+files/0001-use-lazy-umount-when-umount-returns-EBUSY.patch
>

[Daniel Lezcano (daniel-lezcano)]

On 10/08/2010 12:44 PM, Royston Carter wrote:
> Daniel,
> Can we step back a little here please. I have never to date amended
> or patched a Linux component/application so could do with your second
> step explaining. You say "* cd<lxc-topmost-dir> " but does this assume
> I have lxc source installed? If this is required could you add a line
> for how I get this.
>
> Thanks for you response to this.
>

Sure, but let's switch to a private mail exchange, as that will be out
of the scope of this bug.
I will use your contact user in launchpad.

   -- Daniel

[Chuck Short (zulcss)]

This is fixed in natty.

chuck

[Royston Carter (rpcarter)]

Is the fix likely to be back ported to Lucid?

On 01/03/2011 14:27, Chuck Short wrote:
> This is fixed in natty.
>
> chuck
>
> ** Changed in: lxc (Ubuntu)
> Status: New => Fix Released
>