Containers vs Virtualization or Containers + Virtualiztion

Jonathan Frappier Virtxpert

Containers have been a hot topic of late, many are suggesting it is the next step in the virtualization evolution and spells doom for vSphere, Hyper-V or other “traditional” virtualization platforms.  For those who are not aware of containers, its is a packaged application that can run isolated from other applications.  It is not too dissimilar from ThinApps in a virtual desktop environment but focused on server applications such as Apache, Tomcat or other custom applications on top of a single Operating System.

Traditional OS level virtualization generally looks something like this:


Some, such as Linux Journal suggest it is the future and that traditional OS level virtualization and the hypervisor is not needed.  With containers, you could remove the hypervisor layer and run your OS directly on baremetal and run the “virtualized” applications helping to save resources (including budget) which would look something like this:


You can read more about Linux Journal’s take on Containers here:  Containers—Not Virtual Machines—Are the Future Cloud | Linux Journal

There seems to be a small group who think – as it generally is with most technology, that traditional OS/hypervisor virtualization and containers are complimentary.  Scott Lowe has a blog post here walking through the initial setting up along with some thoughts on LXC:  A Brief Introduction to Linux Containers with LXC – – The weblog of an IT pro specializing in virtual…

My question is, why does it have to be Containers versus Virtualization?  Why can’t it be a marriage of the two technologies to offer the best of each, or something like this:


With this model, you can still isolate and manage resources at the OS level which has been proven over and over again as well as drop containers on top of the virtualized OS?  Not only can I still leverage hypervisor features such as high availability, but I can reduce the number of VM’s needed by adding more containers to a single VM.  Scale up resources when needed for adding containers OR scale out resources when needed for redundancy or additional throughput?  What are your thoughts?

You can find out more about popular container at the following sites:

Parallels: OS Virtualization Solution for Windows and Linux — Parallels Virtuozzo Containers – Parallels

Docker:  Docker – Build, Ship, and Run Any App, Anywhere


lmctfy (Google):

Containers vs Virtualization or Containers + Virtualiztion