So technically hypervisor based stuff is a full isolation, and to the base operating system, the guest system looks as an independent host, which has no relation to itself.Ĭontainers share the same kernel which the base operating system is using. Hypervisor based virtualization technologies require a virtual hardware that needs to be created, on top of which an operating system with its own kernel and drivers are installed. Unlike other types of virtualization, containers are much light weight and has less overhead. Read: Main Difference between Containers and Hypervisors If you are quite new to container based virtualization, and is interested in understanding the major difference between a hyper-visor and container based virtualization, then i would recommend reading the below article before going ahead.
And so many companies have already started adopting it as part of their continues integration environment. Developers can now easily ship applications and its entire dependencies inside to anywhere and have the guarantee that it will run anywhere. The main thing that made it popular is the flexibility with which it manages containers and its applications inside it. But a new implementation of container based virtualization has really made it a hot thing for application developers and administrators.
Container based virtualization is not a new thing at all.
0 kommentar(er)
