Docker Multiple Hines Full Of Excellent

The benefit of a hosted hypervisor is that the underlying hardware is less important.

Itd be hard not to, with all the attention its getting these days from developers and system admins alike.

Regardless of whether or not you have an immediate use-case in mind for Docker, I still think its important to understand some of the fundamental concepts around what a container is and how it compares to a Virtual Machine (VM).

Docker Multiple Hines Full Of Excellent

While the Internet is full of excellent usage guides for Docker, I couldnt find many beginner-friendly conceptual guides, particularly on what a container is made up of.

So, hopefully, this post will solve that problem:) Lets start by understanding what VMs and containers even are.

What are containers and VMs Containers and VMs are similar in their goals: to isolate an application and its dependencies into a self-contained unit that can run anywhere.

Moreover, containers and VMs remove the need for physical hardware, allowing for more efficient use of computing resources, both in terms of energy consumption and cost effectiveness.

The main difference between containers and VMs is in their architectural approach.

Virtual Machines A VM is essentially an emulation of a real computer that executes programs like a real computer.

A hypervisor, in turn, runs on either a host machine or on bare-metal.

The hypervisors themselves run on physical computers, referred to as the host machine.

The host machine provides the VMs with resources, including RAM and CPU.

These resources are divided between VMs and can be distributed as you see fit.

So if one VM is running a more resource heavy application, you might allocate more resources to that one than the other VMs running on the same host machine.

The VM that is running on the host machine (again, using a hypervisor) is also often called a guest machine.

This guest machine contains both the application and whatever it needs to run that application (e.g.

It also carries an entire virtualized hardware stack of its own, including virtualized network adapters, storage, and CPU which means it also has its own full-fledged guest operating system.

From the inside, the guest machine behaves as its own unit with its own dedicated resources.

From the outside, we know that its a VM sharing resources provided by the host machine.

As mentioned above, a guest machine can run on either a hosted hypervisor or a bare-metal hypervisor.

For example, a computer running OSX can have a VM (e.g.

VirtualBox or VMware Workstation 8) installed on top of that OS.

The VM doesnt have direct access to hardware, so it has to go through the host operating system (in our case, the Macs OSX).

Docker For Mac Multiple Machines