[lxc-devel] lxc-execute only finds lxc-init when lxc-init is manually populated inside of the container
Peter Fedorow
pfedorow at hcn-inc.com
Wed Mar 26 21:08:31 UTC 2014
How to Reproduce
----------------
1. lxc-create -n test1 -t ubuntu
2. lxc-execute -n test1 -- /bin/bash
Fails:
lxc-execute: Failed to find an lxc-init
3. lxc-start -n test1 -d
4. lxc-console -n test1
5. login
6. sudo apt-get install lxc
7. sudo shutdown -h now
8. lxc-execute -n test1 -- /bin/bash
Success!
LXC Versions Tested
-------------------
Ubuntu automatic upstream - 1.0.1+master~20140326-1500-0ubuntu1~ppa1~saucy1
Ubuntu Trusty - 1.0.1-0ubuntu1
Ubuntu 13.10 - 1.0.0~alpha1-0ubuntu14.1
OS
--
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 13.10
Release: 13.10
Codename: saucy
$ uname -a
Linux bigserver 3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
Additional Notes
----------------
Installing the binary is a work-around for 64-bit, there is no obvious
work-around for 32-bit containers on a 64-bit host.
This is not the same as bug #22. The library is being found, but it
needs to be loaded from outside of the container's rootfs. Providing
the binary alone inside of the container is insufficient unless the
binary is statically linked and 32-bit compatible.
Regards,
Peter Fedorow
--
Manager, Information & Technology Systems
The Hotel Communication Network Inc.
1-613-216-1495 x6235
www.hcn-inc.com
More information about the lxc-devel
mailing list