Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Containers don't replace "hypervisors". They MAY replace "virtual guests". You still need a primary OS On which to put your containers.
The hypervisor is the virtualization platform server (e.g. a VMWare ESX system, a KVM system or a MS Hyper-V system) on which you put your "virtual guest" systems.
At this point far more people are using "virtualization" (Hypervisors and guests) than Containers though there is a lot of buzz about Containers now. You might want to look at CoreOS and RedHat Atomic and Docker for more discussion about what Containers are.
Thus they are two different technologies and Containers based on hypervisors.
Which container have better future? Docker, Linux Container, RedHat Atomic or...
as far as I know Docker is based on Linux Container. Containers are "simple" constructs and hypervisors offer more, but also need more resources. So those are just different levels of virtualization.
I can say that my organization has moved into containers on CoreOS for one major project. Also most of the recent RedHat meetups I've been at have focused RedHat atomic and the speakers there generally suggest that containerization will take the place of virtualization.
However, just because a thing is possible doesn't mean everybody embraces it. At this point I'd suggest most shops are doing some form of virtualization but that doesn't mean they've all abandoned physical systems completely. Factors keeping people on physical include performance and license costs. Similarly many folks these days are moving away from their own virtualization to cloud based systems but here again not everyone has fully embraced the cloud and some things don't make as much sense in public clouds owing to things like the cost of online storage and other add-on costs. In that light containers make sense for some projects but since it is still an emerging technology I don't think you'll see folks abandoning virtualization any time soon.
Containers based on hypervisors and I guess their security problems are more than hypervisors, But if hypervisors dead how Containers live? They are based on hypervisors.
Aha, Thus " without the need for starting any virtual machines" but they use "Operating system level virtualization". According to the "https://en.wikipedia.org/wiki/Operating-system-level_virtualization"
Containers not have any Overhead.
So, They are different technologies.
Not "no" overhead but "less" overhead. The kernel and base OS run at a level above the container and only the specific application component(s) run in the individual container(s). The idea is you should be able to pick and choose what you need for your application distinct from from other applications using the same kernel and base OS. The system with the kernel and the base OS run minimal OS components due to this as the idea is most things you need should come from the container(s) you choose to run.
To this degree the system with the kernel and base OS takes the place of what is a hypervisor in virtualization. The difference is that in full virtualization the hypervisor AND each guest system have full OS installations (where the guests don't have to have the same OS let alone kernel as the hypervisor).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.