1
0
Fork 0
mirror of https://github.com/moby/moby.git synced 2022-11-09 12:21:53 -05:00
Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
Find a file
Jamie Hannaford 7fdf5257b4 Make gofmt use the filename previously referenced
Signed-off-by: Jamie Hannaford <jamie.hannaford@rackspace.com>
2015-03-26 20:39:15 +01:00
api Fix for issue 9922: private registry search with auth returns 401 2015-03-26 18:59:16 +00:00
builder Fixes hacks from progressreader refactor 2015-03-25 18:21:02 -07:00
builtins Remove engine.Status and replace it with standard go error 2015-03-25 22:32:08 +01:00
contrib Merge pull request #11748 from minimum2scp/fix/debootstrap 2015-03-25 16:55:13 -06:00
daemon Merge pull request #11800 from hqhq/hq_fix_create_issue 2015-03-26 11:12:55 -06:00
docker Merge pull request #11566 from tiborvass/carry-10864 2015-03-22 18:21:32 -07:00
dockerinit pkg/reexec: move reexec code to a new package 2014-10-30 14:48:30 +02:00
docs Make gofmt use the filename previously referenced 2015-03-26 20:39:15 +01:00
engine add back job.Errorf 2015-03-26 13:12:36 +08:00
events Fixes hacks from progressreader refactor 2015-03-25 18:21:02 -07:00
graph Fixes hacks from progressreader refactor 2015-03-25 18:21:02 -07:00
hack Merge pull request #11758 from crosbymichael/update-libct-mar25 2015-03-25 12:17:33 -07:00
image when the file that was opened has been read into buffer, the file should be close. 2015-02-27 19:09:17 +08:00
integration Rename Fds to File Descriptors in docker info 2015-03-25 12:04:15 -07:00
integration-cli Merge pull request #11791 from moo-mou/11768-vetwarning 2015-03-26 10:52:07 -07:00
links Env Variables created for each of the ports in addition to env variables for port ranges, regression from #1834 2015-01-15 19:16:31 +00:00
nat nat: enable upper case proto 2015-02-06 14:07:17 +08:00
opts Cleanup redundant else statements find via golint #11602 2015-03-23 20:40:29 +00:00
pkg Merge pull request #11734 from yestin/11601-test-chrootarchive 2015-03-26 11:03:58 -07:00
project Document VERSION file update scheme 2015-03-22 18:45:01 -07:00
registry Fix for issue 9922: private registry search with auth returns 401 2015-03-26 18:59:16 +00:00
runconfig Remove unused runconfig.Config.SecurityOpt field 2015-03-25 15:46:42 -07:00
trust Remove engine.Status and replace it with standard go error 2015-03-25 22:32:08 +01:00
utils Fixes hacks from progressreader refactor 2015-03-25 18:21:02 -07:00
vendor/src Update libcontainer to a6044b701c166fe538fc760f9e2 2015-03-25 11:32:14 -07:00
volumes Fix volume initialize error check, Fixes #11725 2015-03-25 16:36:00 +01:00
.dockerignore Add .dockerignore support 2014-06-26 22:49:08 +00:00
.gitignore Sort .gitignore content 2015-03-24 09:40:07 -07:00
.mailmap Move scripts back to hack/, leave docs in project/ 2015-03-13 14:04:08 -06:00
AUTHORS Move scripts back to hack/, leave docs in project/ 2015-03-13 14:04:08 -06:00
CHANGELOG.md Bump to version v1.5.0 2015-02-10 10:52:36 -08:00
CONTRIBUTING.md CONTRIBUTING.md: fix markdown formating 2015-03-19 01:51:45 -07:00
Dockerfile Revert all but TestPullImageFromCentralRegistry changes 2015-03-24 16:27:35 -07:00
Dockerfile.simple Fail explicitly if curl is missing in contrib/download-frozen-image.sh 2015-03-17 23:10:02 -06:00
LICENSE Update License year to range 2013-2015 2015-01-04 16:59:34 -08:00
MAINTAINERS .: remove trailing white spaces 2015-03-25 13:38:17 -04:00
Makefile Revert "Dealing with trailing whitespaces" 2015-03-25 10:04:56 -06:00
NOTICE .: remove trailing white spaces 2015-03-25 13:38:17 -04:00
README.md We should point README readers at the new registry v2 project 2015-03-19 11:11:51 -04:00
VERSION Bump to version v1.5.0 2015-02-10 10:52:36 -08:00

Docker: the Linux container engine

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 EC2 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 powers 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 L

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 on your local machine as well as servers - both bare metal and virtualized. It is available as a binary on most modern Linux systems, or as a VM on Windows, Mac and other systems.

We also offer an interactive tutorial for quickly learning the basics of using Docker.

For up-to-date install instructions, see the Docs.

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

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.

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 http://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.

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.