Windows Server containers and Hyper-V containers

Windows Server containers are isolated behind their own network compartment. This can be allocated a NAT DHCP or Static IP. Each container has an independent session namespace, which helps to provide isolation and security. The kernel object namespace is isolated per container, but it is shared with the same host operating system. The server that runs Windows Server container could be a physical or virtual machine.

Each container also has access to certain CPU and memory resources, along with storage and network capacity: these are controlled at runtime by the administrator, and this ensures a predictable and guaranteed control over processes.

As shown in Figure 4, there are two containers sharing a number of libraries. These packages also depend on a base OS image that describes the underlying operating system, such as Server Core, which has a large number of APIs that Windows supports, such as .NET, IIS, and so on.

Nano Server is also another...