World Library  
Flag as Inappropriate
Email this Article

Docker (software)

 

Docker (software)

Docker
Original author(s) Solomon Hykes
Developer(s) Docker, Inc.
Initial release 13 March 2013 (2013-03-13)
Stable release 1.8.3[1] / 12 August 2015 (2015-08-12)
Written in Go[2]
Operating system Linux[1]
Platform x86-64 with modern Linux kernel
Type Operating system-level virtualization
License Apache License 2.0
Website .com.dockerwww

Docker is an open-source project that automates the deployment of applications inside software containers, by providing an additional layer of abstraction and automation of operating-system-level virtualization on Linux.[5] Docker uses resource isolation features of the Linux kernel such as cgroups and kernel namespaces to allow independent "containers" to run within a single Linux instance, avoiding the overhead of starting and maintaining virtual machines.[6]

The Linux kernel's support for namespaces mostly[7] 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 isolation, 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.[8][9][10]

According to industry analyst firm 451 Research, "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."[11]

Contents

  • Overview 1
    • Integration 1.1
  • History 2
    • Collaboration 2.1
  • See also 3
  • Notes 4
  • References 5
  • External links 6

Overview

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

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

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.[11] 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 since Docker 0.9, or indirectly via libvirt, LXC (Linux Containers) or systemd-nspawn.[10][13]

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.[14][15]

Integration

Docker can be integrated into various infrastructure tools, including Amazon Web Services,[16] Ansible,[17] CFEngine,[18] Chef,[19] Google Cloud Platform,[20] IBM Bluemix,[21] Jelastic,[22] Jenkins,[23] Microsoft Azure,[24] OpenStack Nova,[25] OpenSVC,[26] Puppet,[27] Salt,[28] and Vagrant.[29]

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

The GearD project aims to integrate Docker into the Red Hat's OpenShift Origin PaaS.[31]

History

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

Docker was released as open source in March 2013.[12] 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.[8][13] 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.[33]

A May 2015 analysis showed the following organizations as main contributors to Docker: the Docker team, Red Hat, IBM, Google, Cisco Systems and Amadeus IT Group.[34]

Collaboration

  • On July 23, 2013, dotCloud, Inc., the commercial entity behind Docker, announced that former Gluster and Plaxo CEO Ben Golub had joined the company, citing Docker as the primary future focus of the company.[35]
  • On September 19, 2013, Red Hat and Docker announced a significant collaboration around Fedora, Red Hat Enterprise Linux, and OpenShift.[36]
  • On January 22, 2014, Docker announced that it had completed a $15 million Series B venture capital round, led by Greylock Partners.[37]
  • On July 23, 2014, Docker acquired Orchard, makers of Fig.[38]
  • On September 16, 2014, Docker announced that it had completed a $40 M Series C round, led by Sequoia Capital.[39]
  • 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.[40][41]
  • 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.[42]
  • 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.[43][44]

See also

Notes

  1. ^ Docker on non-Linux platforms uses a Linux virtual machine to run the containers.[3][4]

References

  1. ^
  2. ^
  3. ^ https://docs.docker.com/installation/windows/#virtual
  4. ^ https://docs.docker.com/installation/mac/#VM
  5. ^
  6. ^
  7. ^
  8. ^ a b
  9. ^
  10. ^ a b c
  11. ^ a b
  12. ^ a b
  13. ^ a b
  14. ^
  15. ^
  16. ^
  17. ^
  18. ^
  19. ^
  20. ^
  21. ^
  22. ^
  23. ^
  24. ^
  25. ^
  26. ^
  27. ^
  28. ^
  29. ^
  30. ^
  31. ^
  32. ^
  33. ^
  34. ^
  35. ^
  36. ^
  37. ^
  38. ^
  39. ^
  40. ^
  41. ^
  42. ^
  43. ^
  44. ^

External links

  • Official website
  • Source code repository
  • Multi-tenancy using Docker
  • Docker 101 Tutorial
  • libcontainer git repo
  • Linux Containers and the future cloud, by Rami Rosen
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 



Copyright © World Library Foundation. All rights reserved. eBooks from World eBook Library are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.