Docker (software)

From Wikipedia, the free encyclopedia
Jump to: navigation, search
This article is about virtualization software. For the desktop icon docker, see Dock (computing). For company, see Docker, Inc. For other uses, see Docker (disambiguation).
Docker (container engine) logo.svg
Original author(s) Solomon Hykes
Developer(s) Docker, Inc.
Initial release 13 March 2013; 4 years ago (2013-03-13)
Stable release
17.03.0-ce[1] / 1 March 2017; 55 days ago (2017-03-01)
Written in Go[2]
Operating system Linux,[a] Windows
Platform x86-64, ARM (experimental) with modern Linux kernel, or x86-64 Windows with Hyper-V capabilities
Type Operating-system-level virtualization
License Apache License 2.0

Docker is an open-source project that automates the deployment of applications inside software containers. Quote of features from Docker web pages:

Docker containers wrap up a piece of software in a complete filesystem that contains everything it needs to run: code, runtime, system tools, system libraries – anything you can install on a server. This guarantees that it will always run the same, regardless of the environment it is running in.[5]

Docker provides an additional layer of abstraction and automation of operating-system-level virtualization on Windows and Linux.[6] Docker uses the resource isolation features of the Linux kernel such as cgroups and kernel namespaces, and a union-capable file system such as OverlayFS and others[7] to allow independent "containers" to run within a single Linux instance, avoiding the overhead of starting and maintaining virtual machines.[8]

The Linux kernel's support for namespaces mostly[9] isolates an application's view of the operating environment, including process trees, network, user IDs and mounted file systems, while the kernel's cgroups provide resource limiting, including the CPU, memory, block I/O, and network. Since version 0.9, Docker includes the libcontainer library as its own way to directly use virtualization facilities provided by the Linux kernel, in addition to using abstracted virtualization interfaces via libvirt, LXC (Linux Containers) and systemd-nspawn.[10][11][12]


Docker can use different interfaces to access virtualization features of the Linux kernel.[12]

As actions are done to a Docker base image, union file system layers are created and documented, such that each layer fully describes how to recreate an action. This strategy enables Docker's lightweight images, as only layer updates need to be propagated (compared to full VMs, for example).

According to a article,

Docker is a tool that can package an application and its dependencies in a virtual container that can run on any Linux server. This helps enable flexibility and portability on where the application can run, whether on premises, public cloud, private cloud, bare metal, etc.[13]

Docker implements a high-level API to provide lightweight containers that run processes in isolation.[14]

Building on top of facilities provided by the Linux kernel (primarily cgroups and namespaces), a Docker container, unlike a virtual machine, does not require or include a separate operating system.[13] Instead, it relies on the kernel's functionality and uses resource isolation (CPU, memory, block I/O, network, etc.) and separate namespaces to isolate the application's view of the operating system. Docker accesses the Linux kernel's virtualization features either directly using the libcontainer library, which is available as of Docker 0.9, or indirectly via libvirt, LXC (Linux Containers) or systemd-nspawn.[12][15]

Because Docker containers are so lightweight, a single server or virtual machine can run several containers simultaneously. A 2016 analysis found that a typical Docker use case involves running five containers per host, but that many organizations run 10 or more.[16]

By using containers, resources can be isolated, services restricted, and processes provisioned to have an almost completely private view of the operating system with their own process ID space, file system structure, and network interfaces. Multiple containers share the same kernel, but each container can be constrained to only use a defined amount of resources such as CPU, memory and I/O.

Using Docker to create and manage containers may simplify the creation of highly distributed systems by allowing multiple applications, worker tasks and other processes to run autonomously on a single physical machine or across multiple virtual machines. This allows the deployment of nodes to be performed as the resources become available or when more nodes are needed, allowing a platform as a service (PaaS)-style of deployment and scaling for systems like Apache Cassandra, MongoDB or Riak. Docker also simplifies the creation and operation of task or workload queues and other distributed systems.[17][18]


Docker can be integrated into various infrastructure tools, including Amazon Web Services,[19] Ansible,[20] CFEngine,[21] Chef,[22] Google Cloud Platform,[23] IBM Bluemix,[24] HPE Helion Stackato, Jelastic,[25] Jenkins,[26] Kubernetes,[27] Microsoft Azure,[28] OpenStack Nova,[29] OpenSVC,[30] Oracle Container Cloud Service,[31] Puppet,[32] Salt,[33] Vagrant,[34] and VMware vSphere Integrated Containers.[35][36]

The Cloud Foundry Diego project integrates Docker into the Cloud Foundry PaaS.[37]

Red Hat's OpenShift PaaS integrates Docker and related project (Kubernetes, Geard, Project Atomic and others) since v3 (June 2015).[38]

The Apprenda PaaS integrates Docker containers in version 6.0 of its product.[39]


Solomon Hykes started Docker in France as an internal project within dotCloud, a platform-as-a-service company,[40] with initial contributions by other dotCloud engineers including Andrea Luzzardi and Francois-Xavier Bourlet.[citation needed] Jeff Lindsay also became involved as an independent collaborator.[citation needed] Docker represents an evolution of dotCloud's proprietary technology, which is itself built on earlier open-source projects such as Cloudlets.[clarification needed][citation needed]

Docker was released as open source in March 2013.[14] On March 13, 2014, with the release of version 0.9, Docker dropped LXC as the default execution environment and replaced it with its own libcontainer library written in the Go programming language.[10][15] As of October 24, 2015, the project had over 25,600 GitHub stars (making it the 20th most-starred GitHub project), over 6,800 forks, and nearly 1,100 contributors.[41]

A May 2016 analysis showed the following organizations as main contributors to Docker: The Docker team, Cisco, Google, Huawei, IBM, Microsoft, and Red Hat.[42]

A January 2017 analysis of LinkedIn profile mentions showed Docker presence grew by 160% in 2016.[43]


  • On September 19, 2013, Red Hat and Docker announced a significant collaboration around Fedora, Red Hat Enterprise Linux, and OpenShift.[44]
  • On October 15, 2014, Microsoft announced integration of the Docker engine into the next (2016) Windows Server release, and native support for the Docker client role in Windows.[45][46]
  • On 10 November 2014, Docker announced a partnership with Stratoscale.[47]
  • On December 4, 2014, IBM announced a strategic partnership with Docker that enables enterprises to more efficiently, quickly and cost-effectively build and run the next generation of applications in the IBM Cloud.[48]
  • On June 22, 2015, Docker and several other companies announced that they are working on a new vendor and operating-system-independent standard for software containers.[49][50]
  • On June 8, 2016, Microsoft announced that Docker now could be used natively on Windows 10 with Hyper-V Containers, to build, ship and run containers utilizing the Windows Server 2016 Technical Preview 5 Nano Server container OS image.[51]
  • On October 4, 2016, Solomon Hykes announced InfraKit as a new self-healing container infrastructure effort for Docker container environments.[52][53]

See also[edit]


  1. ^ Docker on macOS uses a Linux virtual machine to run the containers. It is also possible to run those on Windows using Hyper-V or docker-machine.[3][4]


  1. ^ "Docker Releases". Docker, Inc. 2017-03-01. Retrieved 2017-03-01. 
  2. ^ "Docker source code". Docker, Inc. 2015-10-12. Retrieved 2015-10-24. 
  3. ^ "Redirecting…". Retrieved 9 January 2017. 
  4. ^ "Redirecting…". Retrieved 9 January 2017. 
  5. ^ "What is Docker?". Retrieved 9 January 2017. 
  6. ^ O'Gara, Maureen (26 July 2013). "Ben Golub, Who Sold Gluster to Red Hat, Now Running dotCloud". SYS-CON Media. Retrieved 2013-08-09. 
  7. ^ "Select a storage driver documentation". Docker documentation. Archived from the original on 2016-12-06. Retrieved 2016-12-07. 
  8. ^ "Docker Documentation: Kernel Requirements". 2014-01-04. Archived from the original on 2014-08-21. Retrieved 2014-08-20. 
  9. ^ Dan Walsh. "Yet Another Reason Containers Don't Contain: Kernel Keyrings". Retrieved 13 April 2015. 
  10. ^ a b Steven J. Vaughan-Nichols (2014-06-11). "Docker libcontainer unifies Linux container powers". ZDNet. Retrieved 2014-07-30. 
  11. ^ "libcontainer - reference implementation for containers". Retrieved 2014-07-30. 
  12. ^ a b c "Docker 0.9: Introducing execution drivers and libcontainer". 2014-03-10. Retrieved 2015-01-20. 
  13. ^ a b Noyes, Katherine (1 August 2013). "Docker: A 'Shipping Container' for Linux Code". Retrieved 2013-08-09. 
  14. ^ a b Avram, Abel (2013-03-27). "Docker: Automated and Consistent Software Deployments". InfoQ. Retrieved 2013-08-09. 
  15. ^ a b Swan, Chris (2014-03-13). "Docker drops LXC as default execution environment". InfoQ. Retrieved 2015-01-20. 
  16. ^ "8 surprising facts about real Docker adoption". Datadog. June 2016. Retrieved 2016-11-14. 
  17. ^ Hall, Adron (31 July 2013). "OSCON : Conversations, Deployments, Architecture, Docker and the Future?". CloudAve. Retrieved 2013-08-09. 
  18. ^ Reeder, Travis (22 April 2014). "How Docker Helped Us Achieve the (Near) Impossible". Retrieved 2014-07-25. 
  19. ^ "Amazon EC2 - Docker Documentation". Retrieved 2014-10-18. 
  20. ^ /. "ansible/library/cloud/docker". GitHub. Retrieved 2014-01-20. 
  21. ^ "CFEngine". CFEngine. Retrieved 2014-06-06. 
  22. ^ "thoward/docker-cookbook". GitHub. Retrieved 2014-01-20. 
  23. ^ "Containers on Google Cloud Platform". Google Inc. 
  24. ^ "Bluemix Launches IBM Containers Beta Based on Docker". IBM. 2014-12-04. Retrieved 2015-04-20. 
  25. ^ "Jelastic Announces Docker Integration to Provide the Most Advanced Orchestrated Application Delivery". PRWeb. Retrieved 2014-12-03. 
  26. ^ "georgebashi/jenkins-docker-plugin". GitHub. Retrieved 2017-01-09. 
  27. ^ Surana, Ramit (2015-09-16). "Containerizing Docker on Kubernetes". LinkedIn. Retrieved 2015-11-02. 
  28. ^ "The Docker Virtual Machine Extension for Linux on Azure". Microsoft. 29 June 2015. Retrieved 11 August 2015. 
  29. ^ Stefano Maffulli (2013-06-07). "OpenStack Community Weekly Newsletter (May 31 – June 7) » The OpenStack Blog". Retrieved 2014-01-20. 
  30. ^ "OpenSVC Docker". OpenSVC. Retrieved 2014-05-29. 
  31. ^ Native, Cloud. "Oracle Container Cloud Service Explained By". 
  32. ^ Gareth Rushgrove. "garethr/docker". Puppet Forge. Retrieved 2014-01-20. 
  33. ^ "saltstack/dockerio". Retrieved 2014-01-20. 
  34. ^ "philspitler/vagrant-docker". GitHub. Retrieved 2014-01-20. 
  35. ^ VMware vSphere Integrated Containers (VIC)
  36. ^ VMware’s Photon Platform and How it Treats Containers
  37. ^ Whelan, Phil (2014-09-03). "Cloud Foundry: Diego Explained By Onsi Fakhouri". ActiveState. Retrieved 2015-04-20. Functionality is being added to enable end-users to push Docker images directly into a Cloud Foundry cluster running Diego. 
  38. ^ Jackson, Joab (2014-04-16). "Red Hat to update Docker container tech for enterprises: Open source vendor plans to incorporate advanced Linux tools such as systemd and SELinux into Docker". Computerworld. Computerworld, Inc. Retrieved 2014-05-29. Red Hat has also started a second community project, called GearD, to integrate Docker into its PaaS (platform-as-a-service) hosting software, OpenShift Origin. 
  39. ^ Verge, Jason (2015-04-28). "PaaS and Docker Containers Work Together in Latest Apprenda Release". Data Center Knowledge. Retrieved 2015-12-06. The 6.0 release integrates Docker’s flexibility and portability with the compliance, governance and security capabilities that enterprises need from PaaS. 
  40. ^ "One home for all your apps". Archived from the original on 2014-05-17. Retrieved 2014-05-08. 
  41. ^ "dotcloud/docker". Retrieved 2015-04-13. 
  42. ^ "Docker - Updated project statistics". Gist. Retrieved 2016-08-22. 
  43. ^ Michael Mullany. "Docker Momentum Analysis 2016". Retrieved 2017-01-05. 
  44. ^ "DotCloud Pivots And Wins Big With Docker, The Cloud Service Now Part Of Red Hat OpenShift". TechCrunch. 2013-09-19. Retrieved 2014-01-20. 
  45. ^ Mary Jo Foley (2014-10-15). "Docker container support coming to Microsoft's next Windows Server release". ZDNet. Retrieved 2014-10-16. 
  46. ^ Scott Guthrie (October 15, 2014). "Docker and Microsoft: Integrating Docker with Windows Server and Microsoft Azure". Microsoft. Retrieved 2015-01-12. 
  47. ^ John Rath (10 November 2014). "Stratoscale Raises $32M to Build Docker-Supporting OpenStack Clouds on Commodity Servers". Retrieved 3 January 2016. 
  48. ^ "IBM and Docker Announce Strategic Partnership to Deliver Enterprise Applications in the Cloud and On Prem". IBM. 2014-12-04. Retrieved 2015-04-20. 
  49. ^ Frederic Lardinois (2015-06-22). "Docker, CoreOS, Google, Microsoft, Amazon And Others Come Together To Develop Common Container Standard". TechCrunch. Retrieved 2015-08-08. 
  50. ^ Shirley Siluk (2015-06-22). "Docker, Tech Giants Team on Open Container Project". Retrieved 2015-08-08. 
  51. ^ "Announcing Windows 10 Insider Preview Build 14361". Microsoft. 2016-06-08. Retrieved 2016-06-19. 
  52. ^ Cloud; Apple; Microsoft; Google; Oracle; clouds, Docker emits InfraKit to wrangle containers on competing; disrupter, Dell EMC 'backs' Huawei open-source management; cloud, SETI's mega alien hunt shovels more data onto IBM's. "Docker emits InfraKit to wrangle containers on competing clouds". Retrieved 2016-10-07. 
  53. ^ "Docker Debuts Infrakit Open Source Toolkit for Self-Healing Infrastructure". Retrieved 2016-10-07. 

External links[edit]