Talk about the relationship between Windows native Docker and Windows Server Container, Hyper Container (learning Summary)

It was a good technique to get to Docker when I was learning netcore a while ago. Baidu has a lot of tutorials. Because I used windows to download the installation of a bit to try. But no installation succeeded, only to discover the need to install the VirtualBox virtual machine, conflict with my Hyper-V. later saw the news out of the Windows version of Docker, the VirtualBox replaced by Hyper-V. Also a small surprise, I thought if you can out of the original Windows version of Docker is good. Try to register a docker account, and apply for a beta (jewelery), one months later, did not see the e-mail.

So again Baidu has some information, found the Windows Containers documentation This one website, this is not Windows version of Docker, read after only know, originally is real Windows native Docker, The Windows kernel-based, no longer the original Linux virtual machine. But currently only running on Windows server2016 and Nanoserver, win10 I tried to install a bit, prompting "The Windows Daemon requires Windows Server Technical Preview 5 Build 14300 or later ". winnserver2016 feel a bit large, installed a light-weight version of the Nanoserver, the cost of Dickens finally can use. (see the article especially the tutorial still have to take a step by step slowly to see, urgent not, I was used to what to see what, installation encountered a lot of problems).

Windows version of Docker provides two sets of container technology, one is the server container, which is similar to the Linux Docker, several containers can share the host kernel, the Task Manager can see the corresponding process, the isolation level is relatively low.

Another is the Hyper Container, this is the outside and add a layer of virtual machine, this can provide kernel-level isolation, the container runs in its own kernel, the host task Manager can not see, in fact, is a small virtual machine, this deployment is not troublesome, and the first kind of similar, just need to add "  --isolation=hyperv "parameters such as"Docker run--isolation=hyperv nanoserver ping localhost-t ". Where Naoserver is the OS image. Let's talk about container mirroring.

Container mirroring is divided into two types, one is the OS image and the other is the normal container image, OS image is provided by Microsoft which contains the OS core components. provided by Microsoft. There are now two sets of OS images:

Name                 Version          Source           Summary----                 -------          ------           -------nanoserver           10.0 . 14300.1010   . Technical ... Windowsservercore    10.0. 14300.1000   Technical ...

The other is normal container mirroring, which is based on OS images or other mirrors.

There are two problems that are encountered in the learning process:

The first one is to run Nanosever on Docker, such as Docker run-it ... docker attach ... When the error will need to use Docker remote management, specifically see https://docs.docker.com/engine/security/https/

The second one is to run with the Hyper-V container (--isolation=hyperv) to prompt not enough storage ... I don't know what the reason is now.

For more information, please refer to Windows Containers documentation. Language is best to switch to English, because the updated date of the English article is April, the date of the Chinese translation of the article is February, the difference between the two months, there are a lot of things are different.

Talk about the relationship between Windows native Docker and Windows Server Container, Hyper Container (learning Summary)