Misplaced Pages

Docker (software): Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editNext edit →Content deleted Content addedVisualWikitext
Revision as of 02:28, 6 March 2018 edit177.237.150.206 (talk) →Operation: removed Docker also simplifies the creation and operation of task or workload queues and other distributed systems← Previous edit Revision as of 06:30, 6 March 2018 edit undoCodename Lisa (talk | contribs)55,077 edits Reverted all contributions by 177.237.150.206 because of serious accuracy concerns. For example, the is no "Docker command" tool; Docker itself is a CLI product. There are no different versions; CE and EE are SaaS plans. I've never heard of a resource called "swap"; but swap file falls with the purview of disk resource.Next edit →
Line 146: Line 146:
}}</ref> }}</ref>


Building on top of facilities provided by the ] (primarily cgroups and namespaces), a Docker container, unlike a virtual machine, does not require or include a separate operating system.<ref name="Linux" /> Instead, it relies on the kernel's functionality and uses resource isolation (CPU, memory, swap, block I/O, network, etc.)<ref>https://docs.docker.com/config/containers/resource_constraints/</ref> and ] to isolate the application's view of the operating system. Docker accesses the Linux kernel's virtualization features either directly using the {{Mono|libcontainer}} library, which is available as of Docker&nbsp;0.9, or indirectly via {{Mono|]}}, {{Mono|]}} (Linux Containers) or {{Mono|]}}.<ref name="docker-blog-201403" /><ref name="infoq-201403">{{cite web Building on top of facilities provided by the ] (primarily cgroups and namespaces), a Docker container, unlike a virtual machine, does not require or include a separate operating system.<ref name="Linux" /> Instead, it relies on the kernel's functionality and uses resource isolation (CPU, memory, block I/O, network, etc.) and ] to isolate the application's view of the operating system. Docker accesses the Linux kernel's virtualization features either directly using the {{Mono|libcontainer}} library, which is available as of Docker&nbsp;0.9, or indirectly via {{Mono|]}}, {{Mono|]}} (Linux Containers) or {{Mono|]}}.<ref name="docker-blog-201403" /><ref name="infoq-201403">{{cite web
| last = Swan | last = Swan
| first = Chris | first = Chris
Line 156: Line 156:
}}</ref> }}</ref>


Operating level container technology such as Docker are lighter than other virtualization technologies so allows a single server or virtual machine to 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.<ref> 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.<ref>
{{cite web {{cite web
| title = 8 surprising facts about real Docker adoption | title = 8 surprising facts about real Docker adoption
Line 166: Line 166:
</ref> </ref>


Using containers may simplify the creation of highly ]s 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 ] (PaaS)-style of deployment and scaling for systems like ], ] or ].<ref name="CloudAve">{{cite web Using Docker to create and manage containers may simplify the creation of highly ]s 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 ] (PaaS)-style of deployment and scaling for systems like ], ] or ]. Docker also simplifies the creation and operation of task or workload queues and other distributed systems.<ref name="CloudAve">{{cite web
| last = Hall | last = Hall
| first = Adron | first = Adron
Line 286: Line 286:
}}</ref> 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.<ref>{{cite web|url=https://blogs.windows.com/windowsexperience/2016/06/08/announcing-windows-10-insider-preview-build-14361/|title=Announcing Windows 10 Insider Preview Build 14361|date=2016-06-08|publisher=]|accessdate=2016-06-19}}</ref> }}</ref> 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.<ref>{{cite web|url=https://blogs.windows.com/windowsexperience/2016/06/08/announcing-windows-10-insider-preview-build-14361/|title=Announcing Windows 10 Insider Preview Build 14361|date=2016-06-08|publisher=]|accessdate=2016-06-19}}</ref>


Since then, a feature known as Windows Containers was made available for ] and ]. There are two different types of Windows Containers: "Windows Server Containers" and "Hyper-V Isolation". The former has nothing to do with Docker. The latter, however, is a form of ] (as opposed to OS-level virtualization) and uses Docker to deliver the guest OS image.<ref>{{Cite web|url=https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/|title=Windows Containers|last=Brown|first=Taylor|last2=Childs|first2=Andrew|date=5 February 2016|website=Microsoft Docs|publisher=]|access-date=|last3=Anderson|first3=Rick|last4=Delimarsky|first4=Den|last5=|first5=}}</ref> The guest OS image is a Windows Nano Server image, which is 652 MB in size and has the same limitations of Nano Server,<ref>{{Cite web|url=https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/quick-start-windows-10|title=Windows Container on Windows 10|last=Wenzel|first=Maira|date=29 September 2016|website=Microsoft Docs|publisher=]}}</ref> as well as a separate ].<ref>{{Cite web|url=https://docs.microsoft.com/en-us/virtualization/windowscontainers/images-eula|title=Container OS Image EULA|last=Cooley|first=Sarah|last2=Brown|first2=Taylor|date=5 January 2018|website=Microsoft Docs|publisher=]}}</ref> Since then, a feature known as Windows Containers was made available for ] and ]. There are two different types of Windows Containers: "Windows Server Containers" and "Hyper-V Isolation". The former has nothing to do with Docker. The latter, however, is a form of ] (as opposed to OS-level virtualization) and uses Docker to deliver the guest OS image.<ref>{{Cite web|url=https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/|title=Windows Containers|last=Brown|first=Taylor|last2=Childs|first2=Andrew|date=5 February 2016|website=Microsoft Docs|publisher=]|access-date=|last3=Anderson|first3=Rick|last4=Delimarsky|first4=Den|last5=|first5=}}</ref> The guest OS image is a Windows Nano Server image, which is 652 MB in size and has the same limitations of Nano Server,<ref>{{Cite web|url=https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/quick-start-windows-10|title=Windows Container on Windows 10|last=Wenzel|first=Maira|date=29 September 2016|website=Microsoft Docs|publisher=]}}</ref> as well as a separate ].<ref>{{Cite web|url=https://docs.microsoft.com/en-us/virtualization/windowscontainers/images-eula|title=Container OS Image EULA|last=Cooley|first=Sarah|last2=Brown|first2=Taylor|date=5 January 2018|website=Microsoft Docs|publisher=]}}</ref>


== Components == == Components ==
Line 298: Line 298:


* '''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.<ref>{{Cite web|url=https://docs.docker.com/registry/introduction/|title=About Registry|website=Docker Documentation|language=en-US|access-date=2018-02-26}}</ref><ref name=":0" /> * '''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.<ref>{{Cite web|url=https://docs.docker.com/registry/introduction/|title=About Registry|website=Docker Documentation|language=en-US|access-date=2018-02-26}}</ref><ref name=":0" />

== Versions ==
Docker software is offered in two different versions: Docker CE (Community Edition) and Docker EE (Enterprise Edition).


== Tools == == Tools ==
* '''Docker command''' using <code>docker</code> command written in go, you can do container operation such as create, start, stop and modify containers. Creation of a docker container is done using <code>docker build</code> command an specifying building options using a text file called ''Dockerfile''<ref>https://docs.docker.com/engine/reference/builder/</ref>.
* '''Docker Compose''' is a tool for defining and running multi-container Docker applications.<ref>{{cite web |url=https://docs.docker.com/compose/overview/ |title=Overview of Docker Compose |accessdate=2017-07-06}}</ref> It uses ] files to configure the application's services and performs the creation and start-up process of all the containers with a single command. The <code>docker-compose</code> CLI utility allows users to run commands on multiple containers at once, for example, building images, ] containers, running containers that were stopped, and more.<ref>{{Cite web|url=https://docs.docker.com/compose/reference/|title=Compose command-line reference|website=Docker Documentation|language=en-US|access-date=2018-02-28}}</ref> Commands related to image manipulation, or user-interactive options are not relevant in Docker Compose because they address one container.<ref>{{Cite news|url=https://blog.codeship.com/orchestrate-containers-for-development-with-docker-compose/|title=Orchestrate Containers for Development with Docker Compose|date=2015-05-27|work=via @codeship|access-date=2018-02-28|language=en-US}}</ref> The '''docker-compose.yml''' file is used to define an application’s services and includes various configuration options. For example, the <code>build</code> option defines configuration options such as the Dockerfile path, the <code>command</code> option allows to override default Docker commands, and more.<ref>{{Cite web|url=https://docs.docker.com/compose/compose-file/|title=Compose file version 3 reference|website=Docker Documentation|language=en-US|access-date=2018-02-28}}</ref> The first public version of Docker Compose (version 0.0.1) was released on 21 December 2013.<ref>{{Cite web|url=https://github.com/docker/compose/releases/tag/0.0.1|title=Release 0.0.1|last=Firshman|first=Ben|date=21 December 2013|website=docker/compose|publisher=]|archive-url=|archive-date=|dead-url=|access-date=|via=]}}</ref> The first production-ready version (1.0) was made available on 16 October 2014.<ref>{{Cite web|url=https://github.com/docker/compose/releases/tag/1.0.0|title=Release 1.0.0|last=Prasad|first=Aanand|date=16 October 2014|website=docker/compose|publisher=]|archive-url=|archive-date=|dead-url=|access-date=|via=]}}</ref> * '''Docker Compose''' is a tool for defining and running multi-container Docker applications.<ref>{{cite web |url=https://docs.docker.com/compose/overview/ |title=Overview of Docker Compose |accessdate=2017-07-06}}</ref> It uses ] files to configure the application's services and performs the creation and start-up process of all the containers with a single command. The <code>docker-compose</code> CLI utility allows users to run commands on multiple containers at once, for example, building images, ] containers, running containers that were stopped, and more.<ref>{{Cite web|url=https://docs.docker.com/compose/reference/|title=Compose command-line reference|website=Docker Documentation|language=en-US|access-date=2018-02-28}}</ref> Commands related to image manipulation, or user-interactive options are not relevant in Docker Compose because they address one container.<ref>{{Cite news|url=https://blog.codeship.com/orchestrate-containers-for-development-with-docker-compose/|title=Orchestrate Containers for Development with Docker Compose|date=2015-05-27|work=via @codeship|access-date=2018-02-28|language=en-US}}</ref> The '''docker-compose.yml''' file is used to define an application’s services and includes various configuration options. For example, the <code>build</code> option defines configuration options such as the Dockerfile path, the <code>command</code> option allows to override default Docker commands, and more.<ref>{{Cite web|url=https://docs.docker.com/compose/compose-file/|title=Compose file version 3 reference|website=Docker Documentation|language=en-US|access-date=2018-02-28}}</ref> The first public version of Docker Compose (version 0.0.1) was released on 21 December 2013.<ref>{{Cite web|url=https://github.com/docker/compose/releases/tag/0.0.1|title=Release 0.0.1|last=Firshman|first=Ben|date=21 December 2013|website=docker/compose|publisher=]|archive-url=|archive-date=|dead-url=|access-date=|via=]}}</ref> The first production-ready version (1.0) was made available on 16 October 2014.<ref>{{Cite web|url=https://github.com/docker/compose/releases/tag/1.0.0|title=Release 1.0.0|last=Prasad|first=Aanand|date=16 October 2014|website=docker/compose|publisher=]|archive-url=|archive-date=|dead-url=|access-date=|via=]}}</ref>
* '''Docker Swarm''' provides native ] functionality for Docker containers, which turns a group of Docker engines into a single, virtual Docker engine.<ref>{{cite web |url=https://www.linux.com/news/8-open-source-CONTAINER-ORCHESTRATION-TOOLS-KNOW |title=8 Container Orchestration Tools to Know |date=2017-04-12 |accessdate=2017-07-06}}</ref> In Docker 1.12 and higher, Swarm mode is integrated with Docker Engine.<ref>{{cite web |url=https://docs.docker.com/swarm/ |title=Docker Swarm |accessdate=2017-07-06}}</ref> The <code>swarm</code> CLI utility allows users to run Swarm containers, create discovery tokens, list nodes in the cluster, and more.<ref>{{Cite web|url=https://docs.docker.com/swarm/reference/|title=Swarm command-line reference|website=Docker Documentation|language=en-US|access-date=2018-02-28}}</ref> The <code>docker node</code> CLI utility allows users to run various commands to manage nodes in a swarm, for example, listing the nodes in a swarm, updating nodes, removing nodes from the swarm, and more.<ref>{{Cite web|url=https://docs.docker.com/engine/reference/commandline/node/|title=docker node|website=Docker Documentation|language=en-US|access-date=2018-02-28}}</ref> Docker manages swarms using the ]. According to Raft, for an update to be performed, the majority of Swarm nodes need to agree on the update.<ref>{{Cite web|url=https://www.aquasec.com/display/containers/Docker+Swarm+101|title=Docker Swarm 101|last=|first=|date=|website=aquasec.com|access-date=2018-02-28}}</ref><ref>{{Cite web|url=https://raft.github.io/|title=Raft Consensus Algorithm|website=raft.github.io|language=en|access-date=2018-02-28}}</ref> * '''Docker Swarm''' provides native ] functionality for Docker containers, which turns a group of Docker engines into a single, virtual Docker engine.<ref>{{cite web |url=https://www.linux.com/news/8-open-source-CONTAINER-ORCHESTRATION-TOOLS-KNOW |title=8 Container Orchestration Tools to Know |date=2017-04-12 |accessdate=2017-07-06}}</ref> In Docker 1.12 and higher, Swarm mode is integrated with Docker Engine.<ref>{{cite web |url=https://docs.docker.com/swarm/ |title=Docker Swarm |accessdate=2017-07-06}}</ref> The <code>swarm</code> CLI utility allows users to run Swarm containers, create discovery tokens, list nodes in the cluster, and more.<ref>{{Cite web|url=https://docs.docker.com/swarm/reference/|title=Swarm command-line reference|website=Docker Documentation|language=en-US|access-date=2018-02-28}}</ref> The <code>docker node</code> CLI utility allows users to run various commands to manage nodes in a swarm, for example, listing the nodes in a swarm, updating nodes, removing nodes from the swarm, and more.<ref>{{Cite web|url=https://docs.docker.com/engine/reference/commandline/node/|title=docker node|website=Docker Documentation|language=en-US|access-date=2018-02-28}}</ref> Docker manages swarms using the ]. According to Raft, for an update to be performed, the majority of Swarm nodes need to agree on the update.<ref>{{Cite web|url=https://www.aquasec.com/display/containers/Docker+Swarm+101|title=Docker Swarm 101|last=|first=|date=|website=aquasec.com|access-date=2018-02-28}}</ref><ref>{{Cite web|url=https://raft.github.io/|title=Raft Consensus Algorithm|website=raft.github.io|language=en|access-date=2018-02-28}}</ref>

Revision as of 06:30, 6 March 2018

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).
This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
This article needs to be updated. Relevant discussion may be found on the talk page. Please help update this article to reflect recent events or newly available information. (January 2018)
(Learn how and when to remove this message)
Docker
Original author(s)Solomon Hykes
Developer(s)Docker, Inc.
Initial release13 March 2013; 11 years ago (2013-03-13)
Stable release17.12.1-ce / 27 February 2018; 6 years ago (2018-02-27)
Repositorygithub.com/docker/docker-ce
Written inGo
Operating systemLinux, Windows
Platformx86-64, ARM (experimental)
TypeOperating-system-level virtualization
License
Websitedocker.com

Docker is a computer program that performs operating-system-level virtualization also known as containerization. It is developed by Docker, Inc. Docker is primarily developed for Linux, where it 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 to allow independent "containers" to run within a single Linux instance, avoiding the overhead of starting and maintaining virtual machines (VMs). The Linux kernel's support for namespaces mostly 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 and systemd-nspawn.

A very limited Windows version of Docker is also available.

History

Solomon Hykes started Docker in France as an internal project within dotCloud, a platform-as-a-service company, 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 is itself built on earlier open-source projects such as Cloudlets.

The software debuted to the public in Santa Clara at PyCon in 2013.

Docker was released as open source in March 2013. 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.

In 2015, O'Reilly published a guide to the software, Using Docker written by Adrian Mouat.

Adoption

  • On September 19, 2013, Red Hat and Docker announced a collaboration around Fedora, Red Hat Enterprise Linux, and OpenShift.
  • In November 2014 Docker container services were announced for the Amazon Elastic Compute Cloud (EC2).
  • On November 10, 2014, Docker announced a partnership with Stratoscale.
  • On December 4, 2014, IBM announced a strategic partnership with Docker that enables Docker to integrate more closely with the IBM Cloud.
  • 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.
  • 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.
  • A May 2016 analysis showed the following organizations as main contributors to Docker: The Docker team, Cisco, Google, Huawei, IBM, Microsoft, and Red Hat.
  • On October 4, 2016, Solomon Hykes announced InfraKit as a new self-healing container infrastructure effort for Docker container environments.
  • A January 2017 analysis of LinkedIn profile mentions showed Docker presence grew by 160% in 2016. The software has been downloaded more than 13 billion times as of 2017.

Operation

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

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 Linux.com 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.

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

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. 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.

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.

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.

Integration

Docker can be integrated into various infrastructure tools, including Amazon Web Services, Ansible, CFEngine, Chef, Google Cloud Platform, IBM Bluemix, HPE Helion Stackato, Jelastic, Jenkins, Kubernetes, Microsoft Azure, OpenStack Nova, OpenSVC, Oracle Container Cloud Service, Puppet, Salt, Vagrant, and VMware vSphere Integrated Containers.

The Cloud Foundry Diego project integrates Docker into the Cloud Foundry PaaS.

Nanobox uses Docker (natively and with VirtualBox) containers as a core part of its software development platform.

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

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

Jelastic PaaS provides managed multi-tenant Docker containers with full compatibility to the native ecosystem.

The Tsuru PaaS integrates Docker containers in its product in 2013, the first PaaS to use Docker in a production environment.

For Windows

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

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

Components

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 API requests sent by the Docker Engine API. The Docker client, which identifies itself as "docker", allows users to interact with Docker through CLI. It uses the Docker REST API to communicate with one or more Docker daemons.
  • Objects: Docker objects refer to different entities used to assemble an application in Docker. The main Docker objects are images, containers, and services.
    • A Docker container is a standardized, encapsulated environment that runs applications. A container is managed using the Docker API or CLI.
    • A Docker image is a read-only template used to build containers. Images are used to store and ship applications.
    • A Docker service allows containers to be scaled across multiple Docker daemons. The result is known as a "swarm", cooperating daemons that communicate through the Docker API.
  • 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.

Tools

  • Docker Compose is a tool for defining and running multi-container Docker applications. 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. Commands related to image manipulation, or user-interactive options are not relevant in Docker Compose because they address one container. 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 to override default Docker commands, and more. The first public version of Docker Compose (version 0.0.1) was released on 21 December 2013. The first production-ready version (1.0) was made available on 16 October 2014.
  • Docker Swarm provides native clustering functionality for Docker containers, which turns a group of Docker engines into a single, virtual Docker engine. In Docker 1.12 and higher, Swarm mode is integrated with Docker Engine. The swarm CLI utility allows users to run Swarm containers, create discovery tokens, list nodes in the cluster, and more. 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, removing nodes from the swarm, and more. 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.

See also

Notes

  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.

References

  1. "Docker Releases". docs.docker.com. Docker, Inc. 2018-02-27. Retrieved 2017-07-02.
  2. "Docker source code". docs.docker.com. Docker, Inc. 2015-10-12. Retrieved 2015-10-24.
  3. "Redirecting…". docker.com. Retrieved 9 January 2017.
  4. "Redirecting…". docker.com. Retrieved 9 January 2017.
  5. Michael Friis (2017-03-02). "Announcing Docker Enterprise Edition". Retrieved 2017-03-02.
  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. Vivek Ratan (February 8, 2017). "Docker: A Favourite in the DevOps World". Open Source Forum. Retrieved June 14, 2017.
  8. "Select a storage driver documentation". Docker documentation. Archived from the original on 2016-12-06. Retrieved 2016-12-07. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  9. "Docker Documentation: Kernel Requirements". docker.readthedocs.org. 2014-01-04. Archived from the original on 2014-08-21. Retrieved 2014-08-20.
  10. Dan Walsh. "Yet Another Reason Containers Don't Contain: Kernel Keyrings". projectatomic.io. Retrieved 13 April 2015.
  11. ^ Steven J. Vaughan-Nichols (2014-06-11). "Docker libcontainer unifies Linux container powers". ZDNet. Retrieved 2014-07-30.
  12. "libcontainer - reference implementation for containers". github.com. Retrieved 2014-07-30.
  13. ^ "Docker 0.9: Introducing execution drivers and libcontainer". docker.com. 2014-03-10. Retrieved 2015-01-20.
  14. "One home for all your apps". dotcloud.com. Archived from the original on 2014-05-17. Retrieved 2014-05-08. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  15. "Company snapshot".
  16. ^ Stamey, Laura (26 June 2017). "Docker's Tools of Mass Innovation: Explosive Growth From Open-Source Containers to Commercial Platform for Modernizing and Managing Apps". HostingAdvice.com. Retrieved 29 August 2017.
  17. ^ Avram, Abel (2013-03-27). "Docker: Automated and Consistent Software Deployments". InfoQ. Retrieved 2013-08-09.
  18. ^ Swan, Chris (2014-03-13). "Docker drops LXC as default execution environment". InfoQ. Retrieved 2015-01-20.
  19. "Using Docker by Adrian Mouat".
  20. "DotCloud Pivots And Wins Big With Docker, The Cloud Service Now Part Of Red Hat OpenShift". TechCrunch. 2013-09-19. Retrieved 2014-01-20.
  21. Jeff Barr (November 13, 2014). "Amazon EC2 Container Service (ECS) – Container Management for the AWS Cloud". Amazon Web Services Blog. Retrieved April 29, 2017.
  22. John Rath (10 November 2014). "Stratoscale Raises $32M to Build Docker-Supporting OpenStack Clouds on Commodity Servers". Retrieved 3 January 2016.
  23. "IBM and Docker Announce Strategic Partnership to Deliver Enterprise Applications in the Cloud and On Prem". IBM. 2014-12-04. Retrieved 2015-04-20.
  24. Frederic Lardinois (2015-06-22). "Docker, CoreOS, Google, Microsoft, Amazon And Others Come Together To Develop Common Container Standard". TechCrunch. Retrieved 2015-08-08.
  25. Shirley Siluk (2015-06-22). "Docker, Tech Giants Team on Open Container Project". cio-today.com. Retrieved 2015-08-08.
  26. "dotcloud/docker". github.com. Retrieved 2015-04-13.
  27. "Docker - Updated project statistics". Gist. Retrieved 2016-08-22.
  28. 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. {{cite web}}: |last4= has generic name (help)
  29. "Docker Debuts Infrakit Open Source Toolkit for Self-Healing Infrastructure". www.serverwatch.com. Retrieved 2016-10-07.
  30. Michael Mullany. "Docker Momentum Analysis 2016". Retrieved 2017-01-05.
  31. ^ Noyes, Katherine (1 August 2013). "Docker: A 'Shipping Container' for Linux Code". Linux.com. Retrieved 2013-08-09.
  32. "8 surprising facts about real Docker adoption". Datadog. June 2016. Retrieved 2016-11-14.
  33. Hall, Adron (31 July 2013). "OSCON : Conversations, Deployments, Architecture, Docker and the Future?". CloudAve. Retrieved 2013-08-09.
  34. Reeder, Travis (22 April 2014). "How Docker Helped Us Achieve the (Near) Impossible". Iron.io. Retrieved 2014-07-25.
  35. "Amazon EC2 - Docker Documentation". docs.docker.com. Archived from the original on 2014-10-18. Retrieved 2014-10-18. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  36. /. "ansible/library/cloud/docker". GitHub. Archived from the original on 2013-12-27. Retrieved 2014-01-20. {{cite web}}: |author= has numeric name (help); Unknown parameter |dead-url= ignored (|url-status= suggested) (help)
  37. "CFEngine". CFEngine. Archived from the original on 2014-06-13. Retrieved 2014-06-06. {{cite web}}: Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
  38. "thoward/docker-cookbook". GitHub. Retrieved 2014-01-20.
  39. "Containers on Google Cloud Platform". Google Inc.
  40. "Bluemix Launches IBM Containers Beta Based on Docker". IBM. 2014-12-04. Retrieved 2015-04-20.
  41. "Jelastic Announces Docker Integration to Provide the Most Advanced Orchestrated Application Delivery". PRWeb. Retrieved 2014-12-03.
  42. "georgebashi/jenkins-docker-plugin". GitHub. Retrieved 2017-01-09.
  43. Surana, Ramit (2015-09-16). "Containerizing Docker on Kubernetes". LinkedIn. Retrieved 2015-11-02.
  44. "The Docker Virtual Machine Extension for Linux on Azure". Microsoft. 29 June 2015. Retrieved 11 August 2015.
  45. Stefano Maffulli (2013-06-07). "OpenStack Community Weekly Newsletter (May 31 – June 7) » The OpenStack Blog". Openstack.org. Retrieved 2014-01-20.
  46. "OpenSVC Docker". OpenSVC. Retrieved 2014-05-29.
  47. Native, Cloud. "Oracle Container Cloud Service Explained By Oracle.com".
  48. Gareth Rushgrove. "garethr/docker". Puppet Forge. Retrieved 2014-01-20.
  49. "saltstack/dockerio". Retrieved 2014-01-20.
  50. "philspitler/vagrant-docker". GitHub. Archived from the original on 2013-08-09. Retrieved 2014-01-20. {{cite web}}: Unknown parameter |dead-url= ignored (|url-status= suggested) (help)
  51. http://searchservervirtualization.techtarget.com/definition/VMware-vSphere-Integrated-Containers-VIC VMware vSphere Integrated Containers (VIC)
  52. Fulton III, Scott M. (2015-09-04). "VMware's Photon Platform and How it Treats Containers". The New Stack. Retrieved 2017-06-08.
  53. 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.
  54. Robbins, Richard (2017-06-17). "Docker Containers and the Nanobox Development Platform". Nanobox. Retrieved 2017-06-17. Nanobox uses Docker under the hood for container implementation
  55. 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.
  56. 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.
  57. Fydorenchyk, Tetiana (2017-03-28). "Jelastic Fifth Element Released: Support of Native and Managed Docker Containers". PRWeb. Retrieved 2017-03-28. The tight integration with Docker native solutions reduce the deployment barriers for developers and opens up new business opportunities for hosting providers by redefining economic at scale in hybrid and multi-cloud environments
  58. Medina, Andrews (2013-11-15). "Docker and Tsuru". Docker. Retrieved 2015-12-06.
  59. Mary Jo Foley (2014-10-15). "Docker container support coming to Microsoft's next Windows Server release". ZDNet. Retrieved 2014-10-16.
  60. Scott Guthrie (October 15, 2014). "Docker and Microsoft: Integrating Docker with Windows Server and Microsoft Azure". Microsoft. Retrieved 2015-01-12.
  61. "Announcing Windows 10 Insider Preview Build 14361". Microsoft. 2016-06-08. Retrieved 2016-06-19.
  62. Brown, Taylor; Childs, Andrew; Anderson, Rick; Delimarsky, Den (5 February 2016). "Windows Containers". Microsoft Docs. Microsoft.
  63. Wenzel, Maira (29 September 2016). "Windows Container on Windows 10". Microsoft Docs. Microsoft.
  64. Cooley, Sarah; Brown, Taylor (5 January 2018). "Container OS Image EULA". Microsoft Docs. Microsoft.
  65. ^ "Docker overview". Docker Documentation. Retrieved 2018-02-26.
  66. "dockerd". Docker Documentation. Retrieved 2018-02-26.
  67. "Use the Docker command line". Docker Documentation. Retrieved 2018-02-26.
  68. "The Docker Ecosystem: An Introduction to Common Components | DigitalOcean". www.digitalocean.com. Retrieved 2018-02-26.
  69. "About Registry". Docker Documentation. Retrieved 2018-02-26.
  70. "Overview of Docker Compose". Retrieved 2017-07-06.
  71. "Compose command-line reference". Docker Documentation. Retrieved 2018-02-28.
  72. "Orchestrate Containers for Development with Docker Compose". via @codeship. 2015-05-27. Retrieved 2018-02-28.
  73. "Compose file version 3 reference". Docker Documentation. Retrieved 2018-02-28.
  74. Firshman, Ben (21 December 2013). "Release 0.0.1". docker/compose. Docker, Inc. – via GitHub. {{cite web}}: Cite has empty unknown parameter: |dead-url= (help)
  75. Prasad, Aanand (16 October 2014). "Release 1.0.0". docker/compose. Docker, Inc. – via GitHub. {{cite web}}: Cite has empty unknown parameter: |dead-url= (help)
  76. "8 Container Orchestration Tools to Know". 2017-04-12. Retrieved 2017-07-06.
  77. "Docker Swarm". Retrieved 2017-07-06.
  78. "Swarm command-line reference". Docker Documentation. Retrieved 2018-02-28.
  79. "docker node". Docker Documentation. Retrieved 2018-02-28.
  80. "Docker Swarm 101". aquasec.com. Retrieved 2018-02-28.
  81. "Raft Consensus Algorithm". raft.github.io. Retrieved 2018-02-28.

External links

Virtualization software
Comparison of platform virtualization software
Hardware
(hypervisors)
Native
Hosted
Specialized
Independent
Tools
Operating
system
OS containers
Application containers
Virtual kernel architectures
Related kernel features
Orchestration
Desktop
Application
Network
See also
See also: List of emulators, List of computer system emulators
Linux containers
Operating-system-level virtualization
Container host operating systems
Container engines
Container cluster managers
Categories: