Friday, 3 June 2016

Understanding containers in Windows Server 2016

Posted by Ashwin Venugopal

Understanding containers
A container is an isolated place where an application run without affecting the rest of the system and also without the system affecting the application. Containers are the next evolution in virtualization.

Components of containers

Container host
This element consists of the computer configured with the containers. It can be a physical computer or a virtual computer.

Container image
This is the state of container. For example, If you install an application onto a container you can then capture image which will have post-installation state. And this image will contain only the changes made by the installation of the application. You can use this image and create a new container from it. 

If a container is running, all the changes made to it are made to its sandbox. These changes can be kept or discarded, as required.

Container operating-system image
Containers are made from images. The first layer of the container hierarchy is on container operating system image.

Container repository
This is where container image along with its dependencies are stored.

Container management system
This helps you to manage your containers by using Windows PowerShell or by using the industry-standard Docker system.

Two types of containers

Windows Server containers.
Provide app isolation by using process and namespace isolation. But these share the operating system kernel with the host and with all other containers running on the host.

Hyper-V containers.
Provide for improved isolation by running each container in an optimized virtual machine. Here the kernel of the host is not shared with the containers.

Thanks for reading.

No comments:

Post a Comment