On 07/06/2012 11:18 AM, Li, Zeyang wrote: > That fixed my problem. million thanks :D > Btw, is there a way to have lxc.init while not installing the full lxc > package? Is lxc.init the only thing I need in the container to have > lxc-execute working? > > Zeyang
That's correct, you only need lxc-init. There's no easy way to only install lxc-init though. I supposed you could try to copy lxc-init and liblxc.so.0 to the container without actually installing the package. > On Fri, Jul 6, 2012 at 9:48 PM, Stéphane Graber <stgra...@ubuntu.com> wrote: >> On 07/06/2012 04:09 AM, Ben Butler-Cole wrote: >>> [back on-list] >>> >>> On 6 July 2012 08:59, Li, Zeyang <a.bankn...@gmail.com >>> <mailto:a.bankn...@gmail.com>> wrote: >>> >>> "I also see that you seem to be running the LXC network inside the >>> guest as well as on the host (it too has an lxcbr0 bridge network). Is >>> this intentional?" >>> This is not intentional, but I don't remember ever setting it up so >>> frankly I don't know why it showed. It does have any adverse effect? >>> >>> >>> I think it will appear automatically if you have installed the lxc >>> package on the guest (which should not be necessary unless you are >>> trying to nest containers). I don't know of any adverse effect, but I >>> don't have a good understanding of networking. >>> >>> -Ben >> >> Well, it's actually creating a relatively big mess :) >> >> When you have lxcbr0 on both your host and your container, you'll have >> the following case: >> - host lxcbr0: 10.0.3.1/24 >> - container eth0: 10.0.3.X/24 >> - container lxcbr0: 10.0.3.1/24 >> >> So when you're pining 10.0.3.1 from the container, you're not pinging >> the host at all, you're pinging the container on its lxcbr0 interface. >> >> In short, installing lxc in the container will in most cases cut you >> from the outside world completely. >> >> You have a few ways of fixing this: >> - If you want to use lxcbr0 in that container, then edit >> /etc/default/lxc in the container to change the subnet to something else >> than 10.0.3.0/24, then reboot your container. >> - If you don't want lxcbr0 in the container, also edit /etc/default/lxc >> in the container and set USE_LXC_BRIDGE to false, then reboot the container. >> >> >> After that, all should be back to normal. >> >> -- >> Stéphane Graber >> Ubuntu developer >> http://www.ubuntu.com >> >> -- Stéphane Graber Ubuntu developer http://www.ubuntu.com
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
