Containers Vs Virtual Machine
Containers Vs Virtual Machine
Containers Vs Virtual Machine
virtual machines
Containers and virtual machines are very similar resource virtualization technologies.
Virtualization is the process in which a system singular resource like RAM, CPU, Disk,
or Networking can be ‘virtualized’ and represented as multiple resources.
The key differentiator between containers and virtual machines is that virtual machines
virtualize an entire machine down to the hardware layers and containers only virtualize
software layers above the operating system level.
Runs a complete operating system Runs the user mode portion of an operating
Operating including the kernel, thus requiring system, and can be tailored to contain just
system more system resources (CPU, the needed services for your app, using
memory, and storage). fewer system resources.
Operating Download and install operating Updating or upgrading the operating system
system updates system updates on each VM. files within a container is the same:
and upgrades Installing a new operating system
version requires upgrading or often
just creating an entirely new VM. 1. Edit your container image's build file
This can be time-consuming, (known as a Dockerfile) to point to
especially if you have a lot of the latest version of the Windows
base image.
VMs...
2. Rebuild your container image with
this new base image.
3. Push the container image to your
container registry.
4. Redeploy using an orchestrator.
The orchestrator provides powerful
automation for doing this at scale..
Use a virtual hard disk (VHD) for Use Azure Disks for local storage for a
Persistent local storage for a single VM, or an single node, or Azure Files (SMB shares)
storage SMB file share for storage shared for storage shared by multiple nodes or
by multiple servers servers.