Sip the Windows Server 2016--container container: Concept

Docker is a hot, derivative micro-service platform that attracts countless entrepreneurs. Microsoft, a "traditional" vendor that takes into account operating systems, virtualization platforms, private clouds, and public clouds, has long planned to support container container technology on the Windows platform.

The Great god Mark Russinovich, who began worshipping in the NT era, also published an article last year after joining Microsoft as CTO, detailing the container trends for Windows under the Docker trend. See:

Containers:docker, Windows and Trends

https://azure.microsoft.com/zh-cn/blog/containers-docker-windows-and-trends/

To put it simply, container's architecture is roughly:

650) this.width=650; "Src=" https://i-msdn.sec.s-msft.com/en-us/virtualization/windowscontainers/about/media/ Containerfund.png "" 706 "height="/>

If you understand the architecture of Application Virtualization + Desktop virtualization, it's a bit similar to container. Isolate the OS from the application, process, or sample isolation for loose coupling. The granularity of the container can become finer. You can use sandboxing to implement a container's stateless state and to split the data.

Compare Docker and container to understand faster, there are two very good quick-to-understand pages:

First look at Docker's:

Docker Overview

https://docs.docker.com/engine/understanding-docker/

650) this.width=650; "title=" image "style=" border-left-0px; border-right-width:0px; Background-image:none; border-bottom-width:0px; padding-top:0px; padding-left:0px; padding-right:0px; border-top-width:0px "border=" 0 "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/87/BE/ Wkiom1fgfffy8crtaaeju3gcnjc434.png "width=" 696 "height=" 364 "/>

As you can see, there are some basic elements:

The core is: Docker_host,images,containers,registry

Also need to have: Docker deamon,docker client,dockerfile

In contrast to view Microsoft's

Container Overview

Https://msdn.microsoft.com/en-us/virtualization/windowscontainers/quick_start/quick_start

Core: Container host,container OS image,container image,container Registry

There are also: Dockerfile

The functions of these components are:

Container Host: Hosts that host containers, which can be physical or virtual machines

Container OS Image: Operating system image, providing operating system environment

Container Image: Container mirroring, containing the dependencies of the basic OS, applications, and applications needed to quickly deploy containers

Container Registry: Container registration, container image is stored in the container registration, can be downloaded on demand. This can be either a private registration or a public registration.

Dockerfile: A file used to automatically generate a container image, in a standard format. The Linux and Windows containers that you see in Docker are the same as the framework, but the content is different.

The Windows container itself is divided into two types:

Windows Server Container: Provides application isolation through process and namespace isolation techniques. All Windows Server containers that are running on the host share the host's kernel kernel.

Hyper-V Container: Extends isolation of the Windows Server container to an optimized Hyper-V virtual machine. Containers running on the host are no longer sharing the kernel.

With this concept, the next deployment container will not be as confused as I did an hour ago.

Sip the Windows Server 2016--container container: Concept