Английская Википедия:Docker (software)

Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:About Шаблон:Use mdy dates Шаблон:Infobox software

Файл:Docker (container engine) logo.svg
Former logo

Docker is a set of platform as a service (PaaS) products that use OS-level virtualization to deliver software in packages called containers.[1] The service has both free and premium tiers. The software that hosts the containers is called Docker Engine.[2] It was first released in 2013 and is developed by Docker, Inc.[3]

Docker is a tool that is used to automate the deployment of applications in lightweight containers so that applications can work efficiently in different environments in isolation.

Background

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.[4] Because all of the containers share the services of a single operating system kernel, they use fewer resources than virtual machines.[2]

Operation

Файл:Docker-linux-interfaces.svg
Docker can use different interfaces to access virtualization features of the Linux kernel.[5]

Docker can package an application and its dependencies in a virtual container that can run on any Linux, Windows, or macOS computer. This enables the application to run in a variety of locations, such as on-premises, in public (see decentralized computing, distributed computing, and cloud computing) or private cloud.[6] When running on Linux, 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)[7] to allow containers to run within a single Linux instance, avoiding the overhead of starting and maintaining virtual machines.[8] Docker on macOS uses a Linux virtual machine to run the containers.[9]

Because Docker containers are lightweight, a single server or virtual machine can run several containers simultaneously.[10] A 2018 analysis found that a typical Docker use case involves running eight containers per host, and that a quarter of analyzed organizations run 18 or more per host.[11] It can also be installed on a single board computer like the Raspberry Pi.[12]

The Linux kernel's support for namespaces mostly[13] 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.[14] Since version 0.9, Docker includes its own component (called Шаблон:Mono) to use virtualization facilities provided directly by the Linux kernel, in addition to using abstracted virtualization interfaces via libvirt, LXC and systemd-nspawn.[15][5][6][16]

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

Licensing model

  • The Docker Engine is licensed under the Apache License 2.0. Docker Desktop distributes some components that are licensed under the GNU General Public License.
  • The Dockerfile files can be licensed under an open-source license themselves. The scope of such a license statement is only the Dockerfile and not the container image.

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 requests sent via the Docker Engine API.[18][19] The Docker client program, called docker, provides a command-line interface (CLI) that allows users to interact with Docker daemons.[18][20]
  • Objects: Docker objects are various entities used to assemble an application in Docker. The main classes of Docker objects are images, containers, and services.[18]
    • A Docker container is a standardized, encapsulated environment that runs applications.[21] A container is managed using the Docker API or CLI.[18] It is a process created from an image.
    • A Docker image is a read-only template used to build containers. Images are used to store and ship applications.[18] It is a process image.
    • 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.[18]
  • 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. The main public registry is Docker Hub. Docker Hub is the default registry where Docker looks for images.[18][22] Docker registries also allow the creation of notifications based on events.[23]

An illustrative example of a Dockerfile:[24]

ARG CODE_VERSION=latest
FROM ubuntu:${CODE_VERSION}
COPY ./examplefile.txt /examplefile.txt
ENV MY_ENV_VARIABLE="example_value"
RUN apt-get update

# Mount a directory from the Docker volume
# Note: This is usually specified in the 'docker run' command.
VOLUME ["/myvolume"]

# Expose a port (22 for SSH)
EXPOSE 22

Tools

  • Docker Compose is a tool for defining and running multi-container Docker applications.[25] 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.[26] Commands related to image manipulation, or user-interactive options, are not relevant in Docker Compose because they address one container.[27] 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.[28] The first public beta version of Docker Compose (version 0.0.1) was released on December 21, 2013.[29] The first production-ready version (1.0) was made available on October 16, 2014.[30]
  • Docker Swarm provides native clustering functionality for Docker containers, which turns a group of Docker engines into a single virtual Docker engine.[31] In Docker 1.12 and higher, Swarm mode is integrated with Docker Engine.[32] The docker swarm CLI[33] utility allows users to run Swarm containers, create discovery tokens, list nodes in the cluster, and more.[34] 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.[35] 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.[36][37]
  • Docker Volume facilitates the independent persistence of data, allowing data to remain even after the container is deleted or re-created.[38]

History

Docker Inc. was founded by Kamel Founadi, Solomon Hykes, and Sebastien Pahl[39] during the Y Combinator Summer 2010 startup incubator group and launched in 2011.[40] The startup was also one of the 12 startups in Founder's Den first cohort.[41] Hykes started the Docker project in France as an internal project within dotCloud, a platform-as-a-service company.[42]

Docker debuted to the public in Santa Clara at PyCon in 2013.[43] It was released as open-source in March 2013.[17] 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, libcontainer, which was written in the Go programming language.[15][44]

In 2017, Docker created the Moby project for open research and development.[45]

Adoption

  • September 19, 2013: Red Hat and Docker announced a collaboration around Fedora, Red Hat Enterprise Linux (RHEL), and OpenShift.[46]
  • October 15, 2014: Microsoft announced the integration of the Docker engine into Windows Server, as well as native support for the Docker client role in Windows.[47][48]
  • November 2014: Docker container services were announced for the Amazon Elastic Compute Cloud (EC2).[49]
  • November 10, 2014: Docker announced a partnership with Stratoscale.[50]
  • December 4, 2014: IBM announced a strategic partnership with Docker that enables Docker to integrate more closely with the IBM Cloud.[51]
  • 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.[52][53]
  • December 2015: Oracle Cloud added Docker container support after acquiring StackEngine, a Docker container startup.[54]
  • April 2016: Windocks, an independent software vendor 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.[55]
  • May 2016: analysis showed the following organizations as main contributors to Docker: The Docker team, Cisco, Google, Huawei, IBM, Microsoft, and Red Hat.[56]
  • June 8, 2016: Microsoft announced that Docker could now be used natively on Windows 10.[57]
  • January 2017: An analysis of LinkedIn profile mentions showed Docker presence grew by 160% in 2016.[58]
  • May 6, 2019: Microsoft announced the second version of Windows Subsystem for Linux (WSL). Docker, Inc. announced that it has started working on a version of Docker for Windows that runs on WSL 2.[59] In particular, this means Docker can run on Windows 10 Home (previously it was limited to Windows Pro and Enterprise since it used Hyper-V).
  • August 2020: Microsoft announced a backport of WSL2 to Windows 10 versions 1903 and 1909 (previously WSL2 was available only on version 2004)[60] and Docker developers announced availability of Docker for these platforms.[61]
  • August 2021: Docker Desktop for Windows and MacOS is no longer free for enterprise users. Docker ended free Docker Desktop use for larger business customers and replaced its Free plan with a Personal plan. Docker on Linux distributions remains unaffected.[62]
  • December 2023: Docker acquired AtomicJar to expand its testing capabilities.[63]

See also

Шаблон:Portal

References

Шаблон:Reflist

External links

Шаблон:Virtualization software Шаблон:Linux containers

  1. Ошибка цитирования Неверный тег <ref>; для сносок SYS-CON Media не указан текст
  2. 2,0 2,1 Ошибка цитирования Неверный тег <ref>; для сносок what-is-a-container не указан текст
  3. Ошибка цитирования Неверный тег <ref>; для сносок os4u не указан текст
  4. Ошибка цитирования Неверный тег <ref>; для сносок Auto38-1 не указан текст
  5. 5,0 5,1 Ошибка цитирования Неверный тег <ref>; для сносок docker-blog-2014-03 не указан текст
  6. 6,0 6,1 Ошибка цитирования Неверный тег <ref>; для сносок Linux не указан текст
  7. Ошибка цитирования Неверный тег <ref>; для сносок select-storage-driver не указан текст
  8. Ошибка цитирования Неверный тег <ref>; для сносок kernel-requirements не указан текст
  9. Ошибка цитирования Неверный тег <ref>; для сносок docker-for-mac не указан текст
  10. Ошибка цитирования Неверный тег <ref>; для сносок Chris K., Poweruser 2019 не указан текст
  11. Ошибка цитирования Неверный тег <ref>; для сносок datadog не указан текст
  12. Шаблон:Cite web
  13. Ошибка цитирования Неверный тег <ref>; для сносок kernel-keyrings не указан текст
  14. Ошибка цитирования Неверный тег <ref>; для сносок limit-resources не указан текст
  15. 15,0 15,1 Ошибка цитирования Неверный тег <ref>; для сносок zdnet-7000030397 не указан текст
  16. Ошибка цитирования Неверный тег <ref>; для сносок libcontainer не указан текст
  17. 17,0 17,1 Ошибка цитирования Неверный тег <ref>; для сносок infoq-2013-03 не указан текст
  18. 18,0 18,1 18,2 18,3 18,4 18,5 18,6 Ошибка цитирования Неверный тег <ref>; для сносок docker-overview не указан текст
  19. Ошибка цитирования Неверный тег <ref>; для сносок dockerd не указан текст
  20. Ошибка цитирования Неверный тег <ref>; для сносок cli-usage не указан текст
  21. Ошибка цитирования Неверный тег <ref>; для сносок digitalocean не указан текст
  22. Ошибка цитирования Неверный тег <ref>; для сносок docker-registry не указан текст
  23. Ошибка цитирования Неверный тег <ref>; для сносок Auto38-2 не указан текст
  24. Шаблон:Cite web
  25. Ошибка цитирования Неверный тег <ref>; для сносок compose-overview не указан текст
  26. Ошибка цитирования Неверный тег <ref>; для сносок compose-cli-ref не указан текст
  27. Ошибка цитирования Неверный тег <ref>; для сносок codeship не указан текст
  28. Ошибка цитирования Неверный тег <ref>; для сносок compose-v3-ref не указан текст
  29. Ошибка цитирования Неверный тег <ref>; для сносок release-0.0.1 не указан текст
  30. Ошибка цитирования Неверный тег <ref>; для сносок release-1.0.0 не указан текст
  31. Ошибка цитирования Неверный тег <ref>; для сносок container-orchestration-tools не указан текст
  32. Ошибка цитирования Неверный тег <ref>; для сносок docker-swarm не указан текст
  33. Ошибка цитирования Неверный тег <ref>; для сносок Auto38-3 не указан текст
  34. Ошибка цитирования Неверный тег <ref>; для сносок swarm-cli-ref не указан текст
  35. Ошибка цитирования Неверный тег <ref>; для сносок docker-node не указан текст
  36. Ошибка цитирования Неверный тег <ref>; для сносок aquasec не указан текст
  37. Ошибка цитирования Неверный тег <ref>; для сносок raft не указан текст
  38. Ошибка цитирования Неверный тег <ref>; для сносок myunidockerguide2 не указан текст
  39. Ошибка цитирования Неверный тег <ref>; для сносок Auto38-4 не указан текст
  40. Ошибка цитирования Неверный тег <ref>; для сносок Auto38-5 не указан текст
  41. Ошибка цитирования Неверный тег <ref>; для сносок Auto38-6 не указан текст
  42. Ошибка цитирования Неверный тег <ref>; для сносок dotcloud не указан текст
  43. Ошибка цитирования Неверный тег <ref>; для сносок docker-announcement не указан текст
  44. Ошибка цитирования Неверный тег <ref>; для сносок infoq-2014-03 не указан текст
  45. Ошибка цитирования Неверный тег <ref>; для сносок moby не указан текст
  46. Ошибка цитирования Неверный тег <ref>; для сносок techcrunch-2013-09 не указан текст
  47. Ошибка цитирования Неверный тег <ref>; для сносок docker-windows-server не указан текст
  48. Ошибка цитирования Неверный тег <ref>; для сносок docker-microsoft не указан текст
  49. Ошибка цитирования Неверный тег <ref>; для сносок amazon-ec2 не указан текст
  50. Ошибка цитирования Неверный тег <ref>; для сносок stratoscale не указан текст
  51. Ошибка цитирования Неверный тег <ref>; для сносок ibm-partnership не указан текст
  52. Ошибка цитирования Неверный тег <ref>; для сносок common-container-standard не указан текст
  53. Ошибка цитирования Неверный тег <ref>; для сносок open-container-project не указан текст
  54. Шаблон:Cite web
  55. Ошибка цитирования Неверный тег <ref>; для сносок InfoWorld-Windocks не указан текст
  56. Ошибка цитирования Неверный тег <ref>; для сносок gist-project-stats не указан текст
  57. Ошибка цитирования Неверный тег <ref>; для сносок win10-insider-preview не указан текст
  58. Ошибка цитирования Неверный тег <ref>; для сносок linkedin-pulse не указан текст
  59. Ошибка цитирования Неверный тег <ref>; для сносок Vaughan-Nichols не указан текст
  60. Ошибка цитирования Неверный тег <ref>; для сносок WSL2-backport не указан текст
  61. Ошибка цитирования Неверный тег <ref>; для сносок docker-backport не указан текст
  62. Шаблон:Cite web
  63. Шаблон:Cite web