After updating to lxc-0.8.0-rc3, the behavior I'm seeing is unchanged:
containers that are autostarted at boot work fine, but I am unable to start
commands manually - and the linker can't find liblxc.so.0 after I attempt to
manually load an lxc container, which makes using any of the lxc-commands
impossible.
$ ldd `which lxc-start`
linux-vdso.so.1 => (0x00007fffe37ff000)
liblxc.so.0 => /usr/lib/x86_64-linux-gnu/lxc/liblxc.so.0
(0x00007f76a51f3000)
libcap.so.2 => /lib/libcap.so.2 (0x00007f76a4fc9000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f76a4c41000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f76a4a3e000)
libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 (0x00007f76a483a000)
/lib64/ld-linux-x86-64.so.2 (0x00007f76a5422000)
$ sudo lxc-start -n radius
lxc-start: Invalid argument - pivot_root syscall failed
lxc-start: failed to setup pivot root
lxc-start: failed to set rootfs for 'radius'
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'radius'
$ ldd `which lxc-start`
linux-vdso.so.1 => (0x00007ffff71a5000)
liblxc.so.0 => not found
libcap.so.2 => /lib/libcap.so.2 (0x00007f5f9a681000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5f9a2f9000)
libattr.so.1 => /lib/x86_64-linux-gnu/libattr.so.1 (0x00007f5f9a0f5000)
/lib64/ld-linux-x86-64.so.2 (0x00007f5f9a8ad000)
Is this something that is packaging related, or should I bring up the issue on
the lxc mailing list?
--
Troy Telford
[email protected]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
