Linked by Thom Holwerda on Thu 8th Nov 2007 17:25 UTC, submitted by inkslinger77
"Faster than virtualization, but harder to implement, containers are a promising security technology for Linux. Watch the 2.6.24 kernel for experimental support for creating and managing containers."
Thread beginning with comment 283759
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: I think people have things confused
by CrLf on Fri 9th Nov 2007 10:02
in reply to "I think people have things confused"
Member since:2006-01-03
Yes, this is about the equivalent to Solaris' containers, but the article confuses containers and zones. OpenVZ implements _zones_ (although every guest is running the host's kernel, its userspace isn't shared with the host and can even be a different distribution). Now, you can say that containers are actually the underlying technology for zones, so in that case OpenVZ does implement containers.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-07-08
A Solaris Container is different than a Zone, a Container is used to limit resources used by a specific process or group of processes. For example, if I wanted to limit the number of CPU's "seen" by Oracle for licensing reasons, I would use a Container to accomplish this. Read the folloing PDF's from Oracle and Sun for details:
http://www.oracle.com/corporate/pricing/partitioning.pdf
http://www.sun.com/third-party/global/oracle/consolidation/Containe...
The Computerworld article is talking about making Containers available for Linux, which is an important step in making Linux compete at the same level as Solaris, AIX and HP-UX in the Enterprise arena. From the article:
"Containers" are a form of lightweight virtualization as represented by projects like OpenVZ. While virtualization creates a new virtual machine upon which the guest system runs, containers implementations work by making walls around groups of processes. The result is that, while virtualized guests each run their own kernel (and can run different operating systems than the host), containerized systems all run on the host's kernel."