There had to say about the container of the historical story, following information from the Internet to the income collected:
Container concept began in 1979 proposed UNIX chroot, it is a UNIX operating system calls, the root directory of a process and its child processes changes to the file system in a new location, so that these processes can only access to the new position, so as to achieve the purpose of the process of isolation.
In 2000 FreeBSD has developed a technology similar to container chroot Jails, which is the earliest but also the most versatile container technology. Jails English translation is in prison over the meaning of this "prison" (with the sandbox is more accurate) contains the quarantined file system, user, network, process, etc.
2001 Linux has released its own container technology Linux VServer, 2004 Solaris also released Solaris Containers, both of which will be divided resource, forming a zones, also known as virtual servers.
OpenVZ launched in 2005, which provides virtualization support by the Linux kernel patch, each OpenVZ container full support for the file system, users and groups of users, processes, network isolation, equipment and IPC objects.
In 2007 Google implements Control Groups (cgroups), and added to the Linux kernel, which is epoch-making, provide technical support for the latter part of the container resource quotas.
2008 cgroups based and linux namespace introduced the first most comprehensive Linux containers LXC.
Launched in 2013 up to now the most popular and most widely used container Docker, compared to other early container technology, Docker container introduced a set of ecosystem management, including layered mirror model, the container registry, friendly Rest API .
2014 CoreOS also launched a similar container Rocket Docker's, CoreOS a more lightweight Linux operating system, more stringent on safety than Docker.
2016 is also available on the Microsoft Windows support vessel, Docker can run on Windows natively, rather than requiring the use of Linux virtual machines.
The difference between the virtual machine container
The left is the right of the virtual machine is a container, from the senses, the hierarchy of the virtual machine is obviously more than the container, more than one operating system, and the container is to use the resource isolation and other related technologies in the original operating system to do packaging and implemented in the application layer individually isolated from each other, to achieve the isolation performance loss independent effects similar between virtual machines VM less than this way. A virtual machine is not useless, the virtual machine has its own advantages, such as the way he is the top run multiple operating system instances to do the carrying and isolation, more in line with the operating mechanism of the computer program code migration costs are lower, the container often requires a certain accumulation of technology, in order to better mirror the corresponding container. Overall, the program is no absolute good or bad, only the most suitable for your needs is a good program.
Features container
Sentence summary vessel characteristics:! Build once, Run anywhere (build once, use everywhere)
Docker three core concepts of technology, namely:
● Mirror (Image)
● container (Container)
● warehouse (Repository)
We will expand these in detail in the subsequent description of the actual article, while also introduce more advantages and convenience of the container.
Kubernetes (referred to K8s, is to replace the eight characters "ubernete" made with 8 abbreviation) is a Google open source container orchestration engine. Now that you have a popular product docker, why would derive a k8s and are favored by many clouds and exit their container services in k8s DaaS based on it, it would have to say k8s features:
● aid coordination process to help application integration, maintenance-one "program - Mirror" model.
● Mount Storage Systems
● Distributed confidential information
● Check the program status
● Copy application examples
● a transverse pod automatic scaling
● Naming and Discovery
● Load Balancing
● rollover
● Resource Monitoring
● accessing and reading log
● Debugging
● provide authentication and authorization