please backport lxcguest to lucid

[Serge Hallyn]

The lxcguest package allows a otherwise unmodified ubuntu system to be booted as a container. While lucid currently does not suffice as a containers host (without backported kernel), it is perfectly usable as an LTS guest on non-LTS host. Please backport the lxcguest package to lucid.

[Serge Hallyn (serge-hallyn)]

Backporting lxc 0.7.5 would be great. In order to compile on stock lucid it needs a few packaging tweaks, resulting in the package which built in the ubuntu-virt ppa: https://launchpad.net/~ubuntu-virt/+archive/ppa/+files/lxc_0.7.5-0ubuntu4.10.04.1.dsc

The changes are simply to pull out dh-autoreconf, and set debhelper version to 7 instead of 8.

lxcguest should then work in a lucid guest. lxc itself will work with a backported kernel, though it will refuse to run with the stock lucid kernel.

[Iain Lane (laney)]

Hiya,

On Fri, Aug 19, 2011 at 02:36:52PM -0000, Serge Hallyn wrote:
> Backporting lxc 0.7.5 would be great. In order to compile on stock
> lucid it needs a few packaging tweaks, resulting in the package which
> built in the ubuntu-virt ppa: https://launchpad.net/~ubuntu-
> virt/+archive/ppa/+files/lxc_0.7.5-0ubuntu4.10.04.1.dsc
>
> The changes are simply to pull out dh-autoreconf, and set debhelper
> version to 7 instead of 8.
>
> lxcguest should then work in a lucid guest. lxc itself will work with a
> backported kernel, though it will refuse to run with the stock lucid
> kernel.

If you want 0.7.5 then, in order to ensure a smooth upgrade path for
users with -backports enabled, it'll need to go to M & N as well.

Can you test that the package builds, installs and runs on these
releases and post any debdiffs required for the build?

Is an informative message printed when a newer kernel is required?

Cheers,

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]
PhD student [ <email address hidden> ]

[Serge Hallyn (serge-hallyn)]

Quoting Iain Lane (<email address hidden>):
> Hiya,
>
> On Fri, Aug 19, 2011 at 02:36:52PM -0000, Serge Hallyn wrote:
> > Backporting lxc 0.7.5 would be great. In order to compile on stock
> > lucid it needs a few packaging tweaks, resulting in the package which
> > built in the ubuntu-virt ppa: https://launchpad.net/~ubuntu-
> > virt/+archive/ppa/+files/lxc_0.7.5-0ubuntu4.10.04.1.dsc
> >
> > The changes are simply to pull out dh-autoreconf, and set debhelper
> > version to 7 instead of 8.
> >
> > lxcguest should then work in a lucid guest. lxc itself will work with a
> > backported kernel, though it will refuse to run with the stock lucid
> > kernel.
>
> If you want 0.7.5 then, in order to ensure a smooth upgrade path for
> users with -backports enabled, it'll need to go to M & N as well.

Ok.

> Can you test that the package builds, installs and runs on these
> releases and post any debdiffs required for the build?

Will do.

Is the pointer to the .dsc in my ppa sufficient, or do you want a debdiff
against the version in oneiric for lucid as well?

> Is an informative message printed when a newer kernel is required?

lxc-checkconfig will show:

Network namespace: missing

Attempting to start a container will show:

root@l1:~# lxc-start !*
lxc-start -n ssh1
lxc-start: failed to clone(0x6c020000): Invalid argument
lxc-start: Invalid argument - failed to fork into a new namespace
lxc-start: failed to spawn 'ssh1'
lxc-start: No such file or directory - failed to remove cgroup '/mnt/cgroups/cpu/ssh1'

It does not however explicitly say that a backported kernel will allow lxc
to work.

[Serge Hallyn (serge-hallyn)]

Near as I can tell lucid will have to stick with the older debian/rules, because

dh ${@} --with autotools_dev

 is not supported by lucid.