Open main menu

Docker is a set of platform-as-a-service (PaaS) products that use operating-system-level virtualization to deliver software in packages called containers.[5] Containers are isolated from one another and bundle their own software, libraries and configuration files; they can communicate with each other through well-defined channels.[6] All containers are run by a single operating-system kernel and are thus more lightweight than virtual machines.[7]

Docker
Docker (container engine) logo.svg
Original author(s)Solomon Hykes
Developer(s)Docker, Inc.
Initial releaseMarch 13, 2013; 6 years ago (2013-03-13)
Stable release
19.03.1[1] / July 25, 2019; 23 days ago (2019-07-25)
Repository Edit this at Wikidata
Written inGo[2]
Operating systemLinux, Windows, macOS[a]
Platformx86-64, ARM, s390x, ppc64le
TypeOperating-system-level virtualization
License
Websitewww.docker.com

The service has both free and premium tiers. The software that hosts the containers is called Docker Engine.[7] It was first started in 2013 and is developed by Docker, Inc.[8]

Contents

HistoryEdit

Docker, inc. was founded by Solomon Hykes and Sebastien Pahl during the Y Combinator Summer 2010 startup incubator group and launched in 2011.[9] Hykes started the Docker project in France as an internal project within dotCloud, a platform-as-a-service company.[10] Initial contributors were other dotCloud engineers, including Andrea Luzzardi and Francois-Xavier Bourlet.[11] Jeff Lindsay also became involved as an independent collaborator.[citation needed]

Docker debuted to the public in Santa Clara at PyCon in 2013.[12] It was released as open-source in March 2013.[13] At the time, it used LXC as its default execution environment. One year later, with the release of version 0.9, Docker replaced LXC with its own component, which was written in the Go programming language.[14][15]

AdoptionEdit

  • On September 19, 2013, Red Hat and Docker announced a collaboration around Fedora, Red Hat Enterprise Linux, and OpenShift.[16]
  • In November 2014 Docker container services were announced for the Amazon Elastic Compute Cloud (EC2).[17]
  • On November 10, 2014, Docker announced a partnership with Stratoscale.[18]
  • On December 4, 2014, IBM announced a strategic partnership with Docker that enables Docker to integrate more closely with the IBM Cloud.[19]
  • 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.[20][21]
  • 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.[22]
  • In April 2016, Windocks, an independent ISV released a port of Docker's open source project to Windows, supporting Windows Server 2012 R2 and Server 2016, with all editions of SQL Server 2008 onward.[23]
  • A May 2016 analysis showed the following organizations as main contributors to Docker: The Docker team, Cisco, Google, Huawei, IBM, Microsoft, and Red Hat.[24]
  • A January 2017 analysis of LinkedIn profile mentions showed Docker presence grew by 160% in 2016.[25]

MicrosoftEdit

On October 15, 2014, Microsoft announced the integration of the Docker engine into the next Windows Server release and native support for the Docker client role in Windows.[26][27] 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.[28]

Since then, a feature known as Windows Containers was made available for Windows 10 and Windows Server 2016. There are two types of Windows Containers: "Windows Server Containers" and "Hyper-V Isolation". The former has nothing to do with Docker and falls outside the scope of this article. The latter, however, is a form of hardware virtualization (as opposed to OS-level virtualization) that uses Docker to deliver the guest OS image.[29] This guest OS image is a Windows Nano Server image, which is 652 MB in size,[30] with a separate end-user license agreement.[31]

On May 6, 2019, Microsoft announced the second version of Windows Subsystem for Linux (WSL). This version of WSL integrates a full Linux kernel into Windows 10. As such, Docker, Inc. announced that it has started working on a version of Docker for Windows that runs on WSL 2 instead of a full virtual machine.[32]

OperationEdit

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

According to a Linux.com, Docker 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, or private cloud.[34] 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)[35] to allow containers to run within a single Linux instance, avoiding the overhead of starting and maintaining virtual machines.[36] Because Docker containers are lightweight, a single server or virtual machine can run several containers simultaneously.[37] A 2016 analysis found that a typical Docker use case involves running five containers per host, but that many organizations run 10 or more.[38]

The Linux kernel's support for namespaces mostly[39] 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 for memory and CPU.[40] Since version 0.9, Docker includes its own component (called "libcontainer") to directly use virtualization facilities provided by the Linux kernel, in addition to using abstracted virtualization interfaces via libvirt, LXC and systemd-nspawn.[14][41][33][42]

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

ComponentsEdit

The Docker software as a service offering consists of three components:

  • Software: The Docker daemon, called dockerd, is a persistent process that manages Docker containers and handles container objects. The daemon listens for requests sent via the Docker Engine API.[43][44] The Docker client program, called docker, provides a command-line interface that allows users to interact with Docker daemons.[45][43]
  • Objects: Docker objects are various entities used to assemble an application in Docker. The main classes of Docker objects are images, containers, and services.[43]
    • A Docker container is a standardized, encapsulated environment that runs applications.[46] A container is managed using the Docker API or CLI.[43]
    • A Docker image is a read-only template used to build containers. Images are used to store and ship applications.[43]
    • A Docker service allows containers to be scaled across multiple Docker daemons. The result is known as a swarm, a set of cooperating daemons that communicate through the Docker API.[43]
  • Registries: A Docker registry is a repository for Docker images. Docker clients connect to registries to download ("pull") images for use or upload ("push") images that they have built. Registries can be public or private. Two main public registries are Docker Hub and Docker Cloud. Docker Hub is the default registry where Docker looks for images.[47][43] Docker registries also allow the creation of notifications based on events.[48]

ToolsEdit

  • Docker Compose is a tool for defining and running multi-container Docker applications.[49] It uses YAML files to configure the application's services and performs the creation and start-up process of all the containers with a single command. The docker-compose CLI utility allows users to run commands on multiple containers at once, for example, building images, scaling containers, running containers that were stopped, and more.[50] Commands related to image manipulation, or user-interactive options, are not relevant in Docker Compose because they address one container.[51] The docker-compose.yml file is used to define an application's services and includes various configuration options. For example, the build option defines configuration options such as the Dockerfile path, the command option allows one to override default Docker commands, and more.[52] The first public version of Docker Compose (version 0.0.1) was released on December 21, 2013.[53] The first production-ready version (1.0) was made available on October 16, 2014.[54]
  • Docker Swarm provides native clustering functionality for Docker containers, which turns a group of Docker engines into a single virtual Docker engine.[55] In Docker 1.12 and higher, Swarm mode is integrated with Docker Engine.[56] The swarm CLI utility allows users to run Swarm containers, create discovery tokens, list nodes in the cluster, and more.[57] The docker node CLI utility allows users to run various commands to manage nodes in a swarm, for example, listing the nodes in a swarm, updating nodes, and removing nodes from the swarm.[58] Docker manages swarms using the Raft Consensus Algorithm. According to Raft, for an update to be performed, the majority of Swarm nodes need to agree on the update.[59][60]

See alsoEdit

NotesEdit

  1. ^ Docker on macOS uses a Linux virtual machine to run the containers.[3]

ReferencesEdit

  1. ^ "Releases - docker/docker-ce". Docker, Inc. Retrieved July 25, 2019 – via GitHub.
  2. ^ "Docker source code". docs.docker.com. Docker, Inc. October 12, 2015. Retrieved October 24, 2015.
  3. ^ "Get started with Docker for Mac". docker.com. Retrieved September 27, 2018.
  4. ^ Michael Friis (March 2, 2017). "Announcing Docker Enterprise Edition". Retrieved March 2, 2017.
  5. ^ O'Gara, Maureen (July 26, 2013). "Ben Golub, Who Sold Gluster to Red Hat, Now Running dotCloud". SYS-CON Media. Retrieved August 9, 2013.
  6. ^ "Docker frequently asked questions (FAQ)". March 2, 2019.
  7. ^ a b "What is a Container?". docker.com. Docker, Inc. Retrieved May 13, 2019.
  8. ^ Vivek Ratan (February 8, 2017). "Docker: A Favourite in the DevOps World". Open Source For U. Retrieved June 14, 2017.
  9. ^ "About the dotCloud Platform". dotCloud. Retrieved June 23, 2019.
  10. ^ "One home for all your apps". dotcloud.com. Archived from the original on May 17, 2014. Retrieved May 8, 2014.
  11. ^ "Company snapshot".
  12. ^ "Docker announcement". Retrieved July 13, 2018.
  13. ^ a b Avram, Abel (March 27, 2013). "Docker: Automated and Consistent Software Deployments". InfoQ. Retrieved August 9, 2013.
  14. ^ a b Steven J. Vaughan-Nichols (June 11, 2014). "Docker libcontainer unifies Linux container powers". ZDNet. Retrieved July 30, 2014.
  15. ^ Swan, Chris (March 13, 2014). "Docker drops LXC as default execution environment". InfoQ. Retrieved January 20, 2015.
  16. ^ "DotCloud Pivots And Wins Big With Docker, The Cloud Service Now Part Of Red Hat OpenShift". TechCrunch. September 19, 2013. Retrieved January 20, 2014.
  17. ^ Jeff Barr (November 13, 2014). "Amazon EC2 Container Service (ECS) – Container Management for the AWS Cloud". Amazon Web Services Blog. Retrieved April 29, 2017.
  18. ^ John Rath (November 10, 2014). "Stratoscale Raises $32M to Build Docker-Supporting OpenStack Clouds on Commodity Servers". Retrieved January 3, 2016.
  19. ^ "IBM and Docker Announce Strategic Partnership to Deliver Enterprise Applications in the Cloud and On Prem". IBM. December 4, 2014. Retrieved April 20, 2015.
  20. ^ Frederic Lardinois (June 22, 2015). "Docker, CoreOS, Google, Microsoft, Amazon And Others Come Together To Develop Common Container Standard". TechCrunch. Retrieved August 8, 2015.
  21. ^ Shirley Siluk (June 22, 2015). "Docker, Tech Giants Team on Open Container Project". cio-today.com. Retrieved August 8, 2015.
  22. ^ "dotcloud/docker". github.com. Retrieved April 13, 2015.
  23. ^ Serdar Yegulalp (April 4, 2016). "Windocks does what Docker and Microsoft can't do". Retrieved October 27, 2018.
  24. ^ "Docker – Updated project statistics". Gist. Retrieved August 22, 2016.
  25. ^ Michael Mullany. "Docker Momentum Analysis 2016". Retrieved January 5, 2017.
  26. ^ Mary Jo Foley (October 15, 2014). "Docker container support coming to Microsoft's next Windows Server release". ZDNet. Retrieved October 16, 2014.
  27. ^ Scott Guthrie (October 15, 2014). "Docker and Microsoft: Integrating Docker with Windows Server and Microsoft Azure". Microsoft. Retrieved January 12, 2015.
  28. ^ "Announcing Windows 10 Insider Preview Build 14361". Microsoft. June 8, 2016. Retrieved June 19, 2016.
  29. ^ Brown, Taylor (May 2, 2016). "Windows Containers". Microsoft Docs. Microsoft. Docker is the vessel by which container images are packaged and delivered.
  30. ^ Brown, Taylor (September 29, 2016). "Windows Container on Windows 10". Microsoft Docs. Microsoft.
  31. ^ Cooley, Sarah; Brown, Taylor (January 5, 2018). "Container OS Image EULA". Microsoft Docs. Microsoft.
  32. ^ Vaughan-Nichols, Steven (June 18, 2019). "Docker embraces Windows Subsystem for Linux 2". ZDNet. CBS Interactive.
  33. ^ a b "Docker 0.9: Introducing execution drivers and libcontainer". docker.com. March 10, 2014. Retrieved January 20, 2015.
  34. ^ Cite error: The named reference Linux2 was invoked but never defined (see the help page).
  35. ^ "Select a storage driver documentation". Docker documentation. Archived from the original on December 6, 2016. Retrieved December 7, 2016.
  36. ^ "Docker Documentation: Kernel Requirements". docker.readthedocs.org. January 4, 2014. Archived from the original on August 21, 2014. Retrieved August 20, 2014.
  37. ^ K., Chris (14 January 2019). "Lightweight Windows containers: Using Docker process isolation in Windows 10" (html). Poweruser. Retrieved 2 August 2019. more “lightweight” real containers (via so called process-isolation), where the containerized processes are running directly on the host system — all processes on the host and in the containers are sharing the same Windows kernel. This is similar to how containers on Linux work.
  38. ^ "8 surprising facts about real Docker adoption". Datadog. June 2016. Retrieved November 14, 2016.
  39. ^ Dan Walsh (September 15, 2014). "Yet Another Reason Containers Don't Contain: Kernel Keyrings". projectatomic.io. Retrieved April 13, 2015.
  40. ^ "Limit a container's resources". Docker Documentation. Retrieved March 7, 2018.
  41. ^ "libcontainer – reference implementation for containers". github.com. Retrieved July 30, 2014.
  42. ^ Noyes, Katherine (August 1, 2013). "Docker: A 'Shipping Container' for Linux Code". Linux.com. Retrieved August 9, 2013.
  43. ^ a b c d e f g "Docker overview". Docker Documentation. Retrieved February 26, 2018.
  44. ^ "dockerd". Docker Documentation. Retrieved February 26, 2018.
  45. ^ "Use the Docker command line". Docker Documentation. Retrieved February 26, 2018.
  46. ^ "The Docker Ecosystem: An Introduction to Common Components". www.digitalocean.com. Retrieved February 26, 2018.
  47. ^ "About Registry". Docker Documentation. Retrieved February 26, 2018.
  48. ^ "Work with notifications". March 2, 2019.
  49. ^ "Overview of Docker Compose". Retrieved July 6, 2017.
  50. ^ "Compose command-line reference". Docker Documentation. Retrieved February 28, 2018.
  51. ^ "Orchestrate Containers for Development with Docker Compose". via @codeship. May 27, 2015. Retrieved February 28, 2018.
  52. ^ "Compose file version 3 reference". Docker Documentation. Retrieved February 28, 2018.
  53. ^ Firshman, Ben (December 21, 2013). "Release 0.0.1". docker/compose. Docker, Inc. – via GitHub.
  54. ^ Prasad, Aanand (October 16, 2014). "Release 1.0.0". docker/compose. Docker, Inc. – via GitHub.
  55. ^ "8 Container Orchestration Tools to Know". April 12, 2017. Retrieved July 6, 2017.
  56. ^ "Docker Swarm". Retrieved July 6, 2017.
  57. ^ "Swarm command-line reference". Docker Documentation. Retrieved February 28, 2018.
  58. ^ "docker node". Docker Documentation. Retrieved February 28, 2018.
  59. ^ "Docker Swarm 101". aquasec.com. Retrieved February 28, 2018.
  60. ^ "Raft Consensus Algorithm". raft.github.io. Retrieved February 28, 2018.

Cite error: A list-defined reference named "CloudAve" is not used in the content (see the help page).
Cite error: A list-defined reference named "Iron.io" is not used in the content (see the help page).

External linksEdit