Hi Fajar, Thanks for your response.
I used the debian template and the config file does not (as far as I can tell) have any network related stanzas. Unfortunately this default behaviour lead to the network stack being shared between the host and the container as pointed out by Matthijs. Therefore, I was wondering if there are any other namespaces I should explicitly isolate so as to prevent them being inadvertently shared between host and container. Thanks again for all your help :) Bye for now Jeetu ebrain.in | Beehive Computing Discover and run software from devices around you - share your software and computing resources. A GPLv3 licensed project. On Tue, May 15, 2012 at 2:25 AM, Fajar A. Nugraha <l...@fajar.net> wrote: > On Mon, May 14, 2012 at 11:48 PM, jeetu.gol...@gmail.com > <jeetu.gol...@gmail.com> wrote: > >> Are there other similar instances where I should make specific mention >> in the config file in order to prevent accidental and inadvertent >> sharing of resources between host and container? > > Try creating a container using templates. e.g: > > lxc-create -n test1 -t busybox > > then look at the resulting config file. It provides a good starting point. > > -- > Fajar ------------------------------------------------------------------------------ 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
