Нет описания

Tibor Vass 9623f45fce Remove --network-add and --network-rm flags from service update 9 лет назад
.github eb59238d17 pull-request template: ask for changelog description 9 лет назад
api 9623f45fce Remove --network-add and --network-rm flags from service update 9 лет назад
builder cda10d4d7f Move directive out of globals 9 лет назад
cli ea0d7e5271 Add a script to generate man pages from cobra commands. 9 лет назад
cliconfig ff3e187cc7 Use docker-credential-helpers client to talk with native creds stores. 9 лет назад
cmd 762a73bf7f Split advertised address from listen address 9 лет назад
container c166b2c9da Treat HEALTHCHECK NONE the same as not setting a healthcheck 9 лет назад
contrib 0a4abdb0ac Remove the Require on the socket for the rpm 9 лет назад
daemon b49dd20939 Update diff apply test to check sub directories 9 лет назад
distribution 027de801a8 swarm/controller: allow cancellation to propagate 9 лет назад
dockerversion c44e7a3e63 Pass upstream client's user agent through to registry on operations beyond pulls 9 лет назад
docs 9623f45fce Remove --network-add and --network-rm flags from service update 9 лет назад
errors 526abc00b1 Fix authorization issue - when request is denied return forbbiden exist code (403). 9 лет назад
experimental 4cd455a8d9 fix typos 9 лет назад
hack 4f369a74fa Vendoring libnetwork to avoid a deadlock 9 лет назад
image e111f0c7b2 Fix calculation of relative path for symlink on docker save 9 лет назад
integration-cli 2f736927a0 cli: `docker service|node|stack ps` instead of tasks 9 лет назад
layer 6a5a150722 fix some typos 9 лет назад
libcontainerd eddee8e932 Check if the container is running if no event 9 лет назад
man a0d1201e02 Require listen address and advertise address to be an IP address or an interface name 9 лет назад
migrate ea3cbd3274 Safer file io for configuration files 9 лет назад
oci 86d8758e2b Get the Docker Engine to build clean on Solaris 9 лет назад
opts 43014ea54b Fix opts tests after default port fix 9 лет назад
pkg 3fba11f7c6 Fix files in subdirectories creating bad whiteout 9 лет назад
plugin 52b078fb37 Handle plugin shutdown when liveRestore is set. 9 лет назад
profiles ad28216987 Move mlock back into the default ungated seccomp profile 9 лет назад
project edadc2f4d7 Update Golang requirements in PACKAGERS.md 9 лет назад
reference c1be45fa38 fix typos 9 лет назад
registry 4118e0c9ee Improve flag help consistency, and update docs 9 лет назад
restartmanager 6a5a150722 fix some typos 9 лет назад
runconfig 4118e0c9ee Improve flag help consistency, and update docs 9 лет назад
utils 9c4570a958 Replace execdrivers with containerd implementation 9 лет назад
vendor 4f369a74fa Vendoring libnetwork to avoid a deadlock 9 лет назад
volume 4cd455a8d9 fix typos 9 лет назад
.dockerignore 9c8d6edbf1 Add vendor/pkg to .dockerignore 9 лет назад
.gitignore 0c7eab3157 Make dockerd debuggable 9 лет назад
.mailmap 0829581d7e Fix double entry in authors 9 лет назад
AUTHORS 0829581d7e Fix double entry in authors 9 лет назад
CHANGELOG.md 05073a911d Add some ommissions to CHANGELOG and update some swarm commands 9 лет назад
CONTRIBUTING.md 4cd455a8d9 fix typos 9 лет назад
Dockerfile 6c717a5744 Vendor in new containerd 9 лет назад
Dockerfile.aarch64 33a8310bc8 Harmonize containerd commit used by all Dockerfile 9 лет назад
Dockerfile.armhf 33a8310bc8 Harmonize containerd commit used by all Dockerfile 9 лет назад
Dockerfile.gccgo 33a8310bc8 Harmonize containerd commit used by all Dockerfile 9 лет назад
Dockerfile.ppc64le 33a8310bc8 Harmonize containerd commit used by all Dockerfile 9 лет назад
Dockerfile.s390x 33a8310bc8 Harmonize containerd commit used by all Dockerfile 9 лет назад
Dockerfile.simple 33a8310bc8 Harmonize containerd commit used by all Dockerfile 9 лет назад
Dockerfile.windows 47a16dbe31 bump Go to 1.6.3 9 лет назад
LICENSE 4b32d59595 Update LICENSE date 9 лет назад
MAINTAINERS e427e4b108 Add Justin Cormack to maintainers 9 лет назад
Makefile ea0d7e5271 Add a script to generate man pages from cobra commands. 9 лет назад
NOTICE 4b32d59595 Update LICENSE date 9 лет назад
README.md f2fd765450 Fix dotCloud link 9 лет назад
ROADMAP.md 3b65dda2ed Update ROADMAP.md 9 лет назад
VENDORING.md 1e021ff571 Create standard vendor policies. 9 лет назад
VERSION 8eab29edd8 Bump VERSION to v1.12.0 9 лет назад

README.md

Docker: the container engine Release

Docker is an open source project to pack, ship and run any application as a lightweight container.

Docker containers are both hardware-agnostic and platform-agnostic. This means they can run anywhere, from your laptop to the largest cloud compute instance and everything in between - and they don't require you to use a particular language, framework or packaging system. That makes them great building blocks for deploying and scaling web apps, databases, and backend services without depending on a particular stack or provider.

Docker began as an open-source implementation of the deployment engine which powered dotCloud, a popular Platform-as-a-Service. It benefits directly from the experience accumulated over several years of large-scale operation and support of hundreds of thousands of applications and databases.

Docker logo

Security Disclosure

Security is very important to us. If you have any issue regarding security, please disclose the information responsibly by sending an email to security@docker.com and not by creating a github issue.

Better than VMs

A common method for distributing applications and sandboxing their execution is to use virtual machines, or VMs. Typical VM formats are VMware's vmdk, Oracle VirtualBox's vdi, and Amazon EC2's ami. In theory these formats should allow every developer to automatically package their application into a "machine" for easy distribution and deployment. In practice, that almost never happens, for a few reasons:

  • Size: VMs are very large which makes them impractical to store and transfer.
  • Performance: running VMs consumes significant CPU and memory, which makes them impractical in many scenarios, for example local development of multi-tier applications, and large-scale deployment of cpu and memory-intensive applications on large numbers of machines.
  • Portability: competing VM environments don't play well with each other. Although conversion tools do exist, they are limited and add even more overhead.
  • Hardware-centric: VMs were designed with machine operators in mind, not software developers. As a result, they offer very limited tooling for what developers need most: building, testing and running their software. For example, VMs offer no facilities for application versioning, monitoring, configuration, logging or service discovery.

By contrast, Docker relies on a different sandboxing method known as containerization. Unlike traditional virtualization, containerization takes place at the kernel level. Most modern operating system kernels now support the primitives necessary for containerization, including Linux with openvz, vserver and more recently lxc, Solaris with zones, and FreeBSD with Jails.

Docker builds on top of these low-level primitives to offer developers a portable format and runtime environment that solves all four problems. Docker containers are small (and their transfer can be optimized with layers), they have basically zero memory and cpu overhead, they are completely portable, and are designed from the ground up with an application-centric design.

Perhaps best of all, because Docker operates at the OS level, it can still be run inside a VM!

Plays well with others

Docker does not require you to buy into a particular programming language, framework, packaging system, or configuration language.

Is your application a Unix process? Does it use files, tcp connections, environment variables, standard Unix streams and command-line arguments as inputs and outputs? Then Docker can run it.

Can your application's build be expressed as a sequence of such commands? Then Docker can build it.

Escape dependency hell

A common problem for developers is the difficulty of managing all their application's dependencies in a simple and automated way.

This is usually difficult for several reasons:

  • Cross-platform dependencies. Modern applications often depend on a combination of system libraries and binaries, language-specific packages, framework-specific modules, internal components developed for another project, etc. These dependencies live in different "worlds" and require different tools - these tools typically don't work well with each other, requiring awkward custom integrations.

  • Conflicting dependencies. Different applications may depend on different versions of the same dependency. Packaging tools handle these situations with various degrees of ease - but they all handle them in different and incompatible ways, which again forces the developer to do extra work.

  • Custom dependencies. A developer may need to prepare a custom version of their application's dependency. Some packaging systems can handle custom versions of a dependency, others can't - and all of them handle it differently.

Docker solves the problem of dependency hell by giving the developer a simple way to express all their application's dependencies in one place, while streamlining the process of assembling them. If this makes you think of XKCD 927, don't worry. Docker doesn't replace your favorite packaging systems. It simply orchestrates their use in a simple and repeatable way. How does it do that? With layers.

Docker defines a build as running a sequence of Unix commands, one after the other, in the same container. Build commands modify the contents of the container (usually by installing new files on the filesystem), the next command modifies it some more, etc. Since each build command inherits the result of the previous commands, the order in which the commands are executed expresses dependencies.

Here's a typical Docker build process:

FROM ubuntu:12.04
RUN apt-get update && apt-get install -y python python-pip curl
RUN curl -sSL https://github.com/shykes/helloflask/archive/master.tar.gz | tar -xzv
RUN cd helloflask-master && pip install -r requirements.txt

Note that Docker doesn't care how dependencies are built - as long as they can be built by running a Unix command in a container.

Getting started

Docker can be installed either on your computer for building applications or on servers for running them. To get started, check out the installation instructions in the documentation.

Usage examples

Docker can be used to run short-lived commands, long-running daemons (app servers, databases, etc.), interactive shell sessions, etc.

You can find a list of real-world examples in the documentation.

Under the hood

Under the hood, Docker is built on the following components:

Contributing to Docker GoDoc

Master (Linux) Experimental (linux) Windows FreeBSD
Jenkins Build Status Jenkins Build Status Build Status Build Status

Want to hack on Docker? Awesome! We have instructions to help you get started contributing code or documentation.

These instructions are probably not perfect, please let us know if anything feels wrong or incomplete. Better yet, submit a PR and improve them yourself.

Getting the development builds

Want to run Docker from a master build? You can download master builds at master.dockerproject.org. They are updated with each commit merged into the master branch.

Don't know how to use that super cool new feature in the master build? Check out the master docs at docs.master.dockerproject.org.

How the project is run

Docker is a very, very active project. If you want to learn more about how it is run, or want to get more involved, the best place to start is the project directory.

We are always open to suggestions on process improvements, and are always looking for more maintainers.

Talking to other Docker users and contributors

Legal

Brought to you courtesy of our legal counsel. For more context, please see the NOTICE document in this repo.

Use and transfer of Docker may be subject to certain restrictions by the United States and other governments.

It is your responsibility to ensure that your use and/or transfer does not violate applicable laws.

For more information, please see https://www.bis.doc.gov

Licensing

Docker is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.

Other Docker Related Projects

There are a number of projects under development that are based on Docker's core technology. These projects expand the tooling built around the Docker platform to broaden its application and utility.

  • Docker Registry: Registry server for Docker (hosting/delivery of repositories and images)
  • Docker Machine: Machine management for a container-centric world
  • Docker Swarm: A Docker-native clustering system
  • Docker Compose (formerly Fig): Define and run multi-container apps
  • Kitematic: The easiest way to use Docker on Mac and Windows

If you know of another project underway that should be listed here, please help us keep this list up-to-date by submitting a PR.

Awesome-Docker

You can find more projects, tools and articles related to Docker on the awesome-docker list. Add your project there.

Internet Relay Chat (IRC)

IRC is a direct line to our most knowledgeable Docker users; we have both the #docker and #docker-dev group on irc.freenode.net. IRC is a rich chat protocol but it can overwhelm new users. You can search our chat archives.

Read our IRC quickstart guide for an easy way to get started.
Docker Community Forums The Docker Engine group is for users of the Docker Engine project.
Google Groups The docker-dev group is for contributors and other people contributing to the Docker project. You can join this group without a Google account by sending an email to docker-dev+subscribe@googlegroups.com. You'll receive a join-request message; simply reply to the message to confirm your subscribtion.
Twitter You can follow Docker's Twitter feed to get updates on our products. You can also tweet us questions or just share blogs or stories.
Stack Overflow Stack Overflow has over 7000 Docker questions listed. We regularly monitor Docker questions and so do many other knowledgeable Docker users.