mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
246 lines
14 KiB
HTML
246 lines
14 KiB
HTML
|
<!DOCTYPE html>
|
||
|
|
<!--[if lt IE 7]> <html class="no-js lt-ie9 lt-ie8 lt-ie7"> <![endif]-->
|
||
|
|
<!--[if IE 7]> <html class="no-js lt-ie9 lt-ie8"> <![endif]-->
|
||
|
|
<!--[if IE 8]> <html class="no-js lt-ie9"> <![endif]-->
|
||
|
|
<!--[if gt IE 8]><!-->
|
||
|
|
<html class="no-js" xmlns="http://www.w3.org/1999/html"> <!--<![endif]-->
|
||
|
|
<head>
|
||
|
|
<meta charset="utf-8">
|
||
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
|
||
|
|
<title>Docker - the Linux container runtime</title>
|
||
|
|
|
||
|
|
<meta name="description" content="Docker encapsulates heterogeneous payloads in standard containers">
|
||
|
|
<meta name="viewport" content="width=device-width">
|
||
|
|
|
||
|
|
<!-- twitter bootstrap -->
|
||
|
|
<link rel="stylesheet" href="_static/css/bootstrap.min.css">
|
||
|
|
<link rel="stylesheet" href="_static/css/bootstrap-responsive.min.css">
|
||
|
|
|
||
|
|
<!-- main style file -->
|
||
|
|
<link rel="stylesheet" href="_static/css/main.css">
|
||
|
|
|
||
|
|
<!-- vendor scripts -->
|
||
|
|
<script src="_static/js/vendor/jquery-1.9.1.min.js" type="text/javascript" ></script>
|
||
|
|
<script src="_static/js/vendor/modernizr-2.6.2-respond-1.1.0.min.js" type="text/javascript" ></script>
|
||
|
|
|
||
|
|
</head>
|
||
|
|
|
||
|
|
|
||
|
|
<body>
|
||
|
|
|
||
|
|
|
||
|
|
<div class="navbar navbar-fixed-top">
|
||
|
|
<div class="navbar-dotcloud">
|
||
|
|
<div class="container">
|
||
|
|
<a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
|
||
|
|
<span class="icon-bar"></span>
|
||
|
|
<span class="icon-bar"></span>
|
||
|
|
<span class="icon-bar"></span>
|
||
|
|
</a>
|
||
|
|
<a class="brand" href="#"></a>
|
||
|
|
<div class="nav-collapse collapse">
|
||
|
|
<ul class="nav pull-right">
|
||
|
|
<li><a href="#">Introduction</a></li>
|
||
|
|
<li class=""><a href="usage/concepts/docker.html">Usage</a></li>
|
||
|
|
<li><a href="gettingstarted.html">About</a></li>
|
||
|
|
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</div><!--/.nav-collapse -->
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
<div class="container">
|
||
|
|
<div class="row">
|
||
|
|
<div class="text-center">
|
||
|
|
<img src="_static/img/docker-letters-logo.gif">
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="container">
|
||
|
|
<div class="row">
|
||
|
|
|
||
|
|
<div class="span9">
|
||
|
|
<section class="contentblock">
|
||
|
|
|
||
|
|
<h1>Docker - the Linux container runtime</h1>
|
||
|
|
|
||
|
|
<p>Docker encapsulates heterogeneous payloads in <a href="#container">Standard Containers</a>, and runs them on any server with strong guarantees of isolation and repeatability.</p>
|
||
|
|
|
||
|
|
<p>It is a great building block for automating distributed systems: large-scale web deployments, database clusters, continuous deployment systems, private PaaS, service-oriented architectures, etc.</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><em>Heterogeneous payloads</em>: any combination of binaries, libraries, configuration files, scripts, virtualenvs, jars, gems, tarballs, you name it. No more juggling between domain-specific tools. Docker can deploy and run them all.</li>
|
||
|
|
<li><em>Any server</em>: docker can run on any x64 machine with a modern linux kernel - whether it's a laptop, a bare metal server or a VM. This makes it perfect for multi-cloud deployments.</li>
|
||
|
|
<li><em>Isolation</em>: docker isolates processes from each other and from the underlying host, using lightweight containers. </li>
|
||
|
|
<li><em>Repeatability</em>: because containers are isolated in their own filesystem, they behave the same regardless of where, when, and alongside what they run.</li>
|
||
|
|
</ul>
|
||
|
|
</section>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="span3">
|
||
|
|
<section class="contentblock">
|
||
|
|
<h4>Docker will be open source soon</h4>
|
||
|
|
<br>
|
||
|
|
<div id="wufoo-z7x3p3">
|
||
|
|
Fill out my <a href="http://dotclouddocker.wufoo.com/forms/z7x3p3">online form</a>.
|
||
|
|
</div>
|
||
|
|
<script type="text/javascript">var z7x3p3;(function(d, t) {
|
||
|
|
var s = d.createElement(t), options = {
|
||
|
|
'userName':'dotclouddocker',
|
||
|
|
'formHash':'z7x3p3',
|
||
|
|
'autoResize':true,
|
||
|
|
'height':'577',
|
||
|
|
'async':true,
|
||
|
|
'header':'show'};
|
||
|
|
s.src = ('https:' == d.location.protocol ? 'https://' : 'http://') + 'wufoo.com/scripts/embed/form.js';
|
||
|
|
s.onload = s.onreadystatechange = function() {
|
||
|
|
var rs = this.readyState; if (rs) if (rs != 'complete') if (rs != 'loaded') return;
|
||
|
|
try { z7x3p3 = new WufooForm();z7x3p3.initialize(options);z7x3p3.display(); } catch (e) {}};
|
||
|
|
var scr = d.getElementsByTagName(t)[0], par = scr.parentNode; par.insertBefore(s, scr);
|
||
|
|
})(document, 'script');</script>
|
||
|
|
|
||
|
|
<a href="#twitter"><img src="_static/img/twitter.png"> Follow us on Twitter</a>
|
||
|
|
</section>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
<div class="span12">
|
||
|
|
|
||
|
|
<section class="contentblock">
|
||
|
|
|
||
|
|
<img src="_static/lego_docker.jpg" width="600px" style="float:right; margin-left: 10px">
|
||
|
|
<h2>Notable features</h2>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>Filesystem isolation: each process container runs in a completely separate root filesystem.</li>
|
||
|
|
<li>Resource isolation: system resources like cpu and memory can be allocated differently to each process container, using cgroups.</li>
|
||
|
|
<li>Network isolation: each process container runs in its own network namespace, with a virtual interface and IP address of its own.</li>
|
||
|
|
<li>Copy-on-write: root filesystems are created using copy-on-write, which makes deployment extremeley fast, memory-cheap and disk-cheap.</li>
|
||
|
|
<li>Logging: the standard streams (stdout/stderr/stdin) of each process container is collected and logged for real-time or batch retrieval.</li>
|
||
|
|
<li>Change management: changes to a container's filesystem can be committed into a new image and re-used to create more containers. No templating or manual configuration required.</li>
|
||
|
|
<li>Interactive shell: docker can allocate a pseudo-tty and attach to the standard input of any container, for example to run a throwaway interactive shell.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<h2>Under the hood</h2>
|
||
|
|
|
||
|
|
<p>Under the hood, Docker is built on the following components:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>The <a href="http://blog.dotcloud.com/kernel-secrets-from-the-paas-garage-part-24-c">cgroup</a> and <a href="http://blog.dotcloud.com/under-the-hood-linux-kernels-on-dotcloud-part">namespacing</a> capabilities of the Linux kernel;</li>
|
||
|
|
<li><a href="http://aufs.sourceforge.net/aufs.html">AUFS</a>, a powerful union filesystem with copy-on-write capabilities;</li>
|
||
|
|
<li>The <a href="http://golang.org">Go</a> programming language;</li>
|
||
|
|
<li><a href="http://lxc.sourceforge.net/">lxc</a>, a set of convenience scripts to simplify the creation of linux containers.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</section>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="row">
|
||
|
|
<div class="span12">
|
||
|
|
<section id="container" class="contentblock">
|
||
|
|
|
||
|
|
|
||
|
|
<h1>What is a Standard Container?</h1>
|
||
|
|
|
||
|
|
|
||
|
|
<p>Docker defines a unit of software delivery called a Standard Container. The goal of a Standard Container is to encapsulate a software component and all its dependencies in
|
||
|
|
a format that is self-describing and portable, so that any compliant runtime can run it without extra dependency, regardless of the underlying machine and the contents of the container.</p>
|
||
|
|
|
||
|
|
<p>The spec for Standard Containers is currently work in progress, but it is very straightforward. It mostly defines 1) an image format, 2) a set of standard operations, and 3) an execution environment.</p>
|
||
|
|
|
||
|
|
<p>A great analogy for this is the shipping container. Just like Standard Containers are a fundamental unit of software delivery, shipping containers (http://bricks.argz.com/ins/7823-1/12) are a fundamental unit of physical delivery.</p>
|
||
|
|
|
||
|
|
<h3>1. STANDARD OPERATIONS</h3>
|
||
|
|
|
||
|
|
<p>Just like shipping containers, Standard Containers define a set of STANDARD OPERATIONS. Shipping containers can be lifted, stacked, locked, loaded, unloaded and labelled. Similarly, standard containers can be started, stopped, copied, snapshotted, downloaded, uploaded and tagged.</p>
|
||
|
|
|
||
|
|
<h3>2. CONTENT-AGNOSTIC</h3>
|
||
|
|
|
||
|
|
<p>Just like shipping containers, Standard Containers are CONTENT-AGNOSTIC: all standard operations have the same effect regardless of the contents. A shipping container will be stacked in exactly the same way whether it contains Vietnamese powder coffe or spare Maserati parts. Similarly, Standard Containers are started or uploaded in the same way whether they contain a postgres database, a php application with its dependencies and application server, or Java build artifacts.</p>
|
||
|
|
|
||
|
|
<h3>3. INFRASTRUCTURE-AGNOSTIC</h3>
|
||
|
|
|
||
|
|
<p>Both types of containers are INFRASTRUCTURE-AGNOSTIC: they can be transported to thousands of facilities around the world, and manipulated by a wide variety of equipment. A shipping container can be packed in a factory in Ukraine, transported by truck to the nearest routing center, stacked onto a train, loaded into a German boat by an Australian-built crane, stored in a warehouse at a US facility, etc. Similarly, a standard container can be bundled on my laptop, uploaded to S3, downloaded, run and snapshotted by a build server at Equinix in Virginia, uploaded to 10 staging servers in a home-made Openstack cluster, then sent to 30 production instances across 3 EC2 regions.</p>
|
||
|
|
|
||
|
|
<h3>4. DESIGNED FOR AUTOMATION</h3>
|
||
|
|
|
||
|
|
<p>Because they offer the same standard operations regardless of content and infrastructure, Standard Containers, just like their physical counterpart, are extremely well-suited for automation. In fact, you could say automation is their secret weapon.</p>
|
||
|
|
|
||
|
|
<p>Many things that once required time-consuming and error-prone human effort can now be programmed. Before shipping containers, a bag of powder coffee was hauled, dragged, dropped, rolled and stacked by 10 different people in 10 different locations by the time it reached its destination. 1 out of 50 disappeared. 1 out of 20 was damaged. The process was slow, inefficient and cost a fortune - and was entirely different depending on the facility and the type of goods.</p>
|
||
|
|
|
||
|
|
<p>Similarly, before Standard Containers, by the time a software component ran in production, it had been individually built, configured, bundled, documented, patched, vendored, templated, tweaked and instrumented by 10 different people on 10 different computers. Builds failed, libraries conflicted, mirrors crashed, post-it notes were lost, logs were misplaced, cluster updates were half-broken. The process was slow, inefficient and cost a fortune - and was entirely different depending on the language and infrastructure provider.</p>
|
||
|
|
|
||
|
|
<h3>5. INDUSTRIAL-GRADE DELIVERY</h3>
|
||
|
|
|
||
|
|
<p>There are 17 million shipping containers in existence, packed with every physical good imaginable. Every single one of them can be loaded on the same boats, by the same cranes, in the same facilities, and sent anywhere in the World with incredible efficiency. It is embarrassing to think that a 30 ton shipment of coffee can safely travel half-way across the World in <em>less time</em> than it takes a software team to deliver its code from one datacenter to another sitting 10 miles away.</p>
|
||
|
|
|
||
|
|
<p>With Standard Containers we can put an end to that embarrassment, by making INDUSTRIAL-GRADE DELIVERY of software a reality.</p>
|
||
|
|
</section>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="row">
|
||
|
|
<div class="span6">
|
||
|
|
<section class="contentblock">
|
||
|
|
<h3 id="twitter">Twitter</h3>
|
||
|
|
<a class="twitter-timeline" href="https://twitter.com/getdocker" data-widget-id="312730839718957056">Tweets by @getdocker</a>
|
||
|
|
<script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElementById(id)){js=d.createElement(s);js.id=id;js.src="//platform.twitter.com/widgets.js";fjs.parentNode.insertBefore(js,fjs);}}(document,"script","twitter-wjs");</script>
|
||
|
|
</section>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</div> <!-- end row -->
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</div> <!-- end container -->
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<hr>
|
||
|
|
<footer>
|
||
|
|
<div class="row">
|
||
|
|
<div class="text-center">
|
||
|
|
Docker is a project by <a href="http://www.dotcloud.com">dotCloud</a>. When released, find us on <a href="http://github.com/dotcloud/docker/">Github</a>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="row">
|
||
|
|
<div class="emptyspace" style="height: 40px">
|
||
|
|
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</footer>
|
||
|
|
|
||
|
|
<!-- bootstrap javascipts -->
|
||
|
|
<script src="js/vendor/bootstrap.min.js" type="text/javascript"></script>
|
||
|
|
|
||
|
|
<!-- Google analytics -->
|
||
|
|
<script type="text/javascript">
|
||
|
|
|
||
|
|
var _gaq = _gaq || [];
|
||
|
|
_gaq.push(['_setAccount', 'UA-6096819-11']);
|
||
|
|
_gaq.push(['_setDomainName', 'docker.io']);
|
||
|
|
_gaq.push(['_setAllowLinker', true]);
|
||
|
|
_gaq.push(['_trackPageview']);
|
||
|
|
|
||
|
|
(function() {
|
||
|
|
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
|
||
|
|
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
|
||
|
|
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
|
||
|
|
})();
|
||
|
|
|
||
|
|
</script>
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|