On Mon, Oct 10, 2011 at 01:59:10PM -0700, Eric W. Biederman wrote: > Lennart Poettering <mzxre...@0pointer.de> writes: > > > To make a standard distribution run nicely in a Linux container you > > usually have to make quite a number of modifications to it and disable > > certain things from the boot process. Ideally however, one could simply > > boot the same image on a real machine and in a container and would just > > do the right thing, fully stateless. And for that you need to be able to > > detect containers, and currently you can't. > > I agree getting to the point where we can run a standard distribution > unmodified in a container sounds like a reasonable goal.
Hmm, interesting. It's not clear to me that running a full standard distribution in a container is always going to be what everyone wants to do. The whole point of containers versus VM's is that containers are lighter weight. And one of the ways that containers can be lighter weight is if you don't have to have N copies of udev, dbus, running in each container/VM. If you end up so much overhead to provide the desired security and/or performance isolation, then it becomes fair to ask the question whether you might as well pay a tad bit more and get even better security and isolation by using a VM solution.... - Ted ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel