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

Serge Hallyn serge.hallyn at ubuntu.com
Thu Mar 27 14:16:57 UTC 2014


Quoting Stéphane Graber (stgraber at ubuntu.com):
> 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.

Hm, I assumed there was some reason why we couldn't do that.  If there
isn't, I'll go ahead and float a patch...


More information about the lxc-devel mailing list