On 05/21/2010 02:20 PM, Nathan Lynch wrote: > On Fri, 2010-05-21 at 09:56 +0200, Daniel Lezcano wrote: > >> 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. >> > Not to bikeshed this further, but /usr/$libdir/lxc is probably not a > good default value. FHS says applications may use only a single > subdirectory in /usr/lib, and I think it was pointed out on the earlier > thread that Debian and related distros already place lxc components in > this directory. >
If I refer to http://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard /var/tmp/lxc could be a good candidate no ? ------------------------------------------------------------------------------ _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
