[lxc-devel] "use defined rootfs mount point" regression?

Nathan Lynch ntl at pobox.com
Fri May 21 12:20:25 UTC 2010


On Fri, 2010-05-21 at 11:49 +0200, Ferenc Wagner wrote:
> Daniel Lezcano <daniel.lezcano at free.fr> writes:
> 
> > On 05/21/2010 11:14 AM, Ferenc Wagner wrote:
> >
> >> Daniel Lezcano<daniel.lezcano at free.fr>  writes:
> >>    
> >>> On 05/20/2010 10:40 PM, Nathan Lynch wrote:
> >>>      
> >>>> lxc-execute: No such file or directory - failed to access to '/usr/lib64/lxc', check it is present
> >>>> lxc-execute: failed to set rootfs for 'truetest-19794'
> >>>> lxc-execute: failed to setup the container
> >>>>
> >>>> /usr/lib64/lxc does not exist on the host.  Is this the intended
> >>>> behavior?
> >>>        
> >>> Yes, you have to create it. I expect the distro maintainers to update
> >>> their package %post_install section to create the directory.
> >>      
> >> It should probably be a job for lxc's make install as well, though
> >
> > Yes, it's possible. But we have to take care of package generation
> > eg. rpmbuild which creates a temporary install directory.
> 
> Sure, the package generation will generally have to change as well.
> During that, make install is usually called with DESTDIR set to some
> temporary directory, and the packaging tools (at least in Debian) can
> warn the packager is something is left there but was not put in any
> package.

Yes, RPM does this too.  If make install had created this directory the
package build would have broken, which would be better behavior than
failing at runtime.






More information about the lxc-devel mailing list