[lxc-devel] lxc-execute only finds lxc-init when lxc-init is manually populated inside of the container

Stéphane Graber stgraber at ubuntu.com
Wed Mar 26 23:07:07 UTC 2014


On Wed, Mar 26, 2014 at 06:03:15PM -0500, Serge Hallyn wrote:
> Quoting Stéphane Graber (stgraber at ubuntu.com):
> > So the best way around this (which is arguably not ideal) is to install
> > lxc (the 32bit version) inside the container and just symlink that
> > lxc-init to /usr/lib/x86_64-linux-gnu/lxc/lxc-init in that container.
> > 
> > I guess we should make the path to lxc-init configurable somehow to deal
> > with that corner case.
> 
> Showing my disdain for some of the current standards...  Given that
> lxc-init is simply an *init*, how about calling it /sbin/init.lxc?

I'm fine with that, I'd just like us to avoid calling it lxc-init in a
location that's part of PATH because that'd likely confuse some users
who would run it directly.

-- 
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.linuxcontainers.org/pipermail/lxc-devel/attachments/20140326/be710243/attachment.pgp>


More information about the lxc-devel mailing list