On Thu, 13 Jun 2013 10:09:59 -0500
Serge Hallyn wrote:
> Currently due to some safety checks for !rootfs.path, lxc-execute
> works ok if you do not set lxc.rootfs at all in your lxc.conf. But if
> you set lxc.rootfs = '/', then it sets up console, and when you do an
> lxc-execute, the console app
On Thu, Jun 13, 2013 at 10:09:59AM -0500, Serge Hallyn wrote:
> Currently due to some safety checks for !rootfs.path, lxc-execute works
> ok if you do not set lxc.rootfs at all in your lxc.conf. But if you
> set lxc.rootfs = '/', then it sets up console, and when you do an
> lxc-execute, the consol
Currently due to some safety checks for !rootfs.path, lxc-execute works
ok if you do not set lxc.rootfs at all in your lxc.conf. But if you
set lxc.rootfs = '/', then it sets up console, and when you do an
lxc-execute, the console appears hung.
However the lxc.rootfs NULL check was just incidental
