Bump to 0.7.0-rc7

.gitignore

@@ -1,6 +1,3 @@
-# Docker project generated files to ignore
-#  if you want to ignore files created by your editor/tools,
-#  please consider a global .gitignore https://help.github.com/articles/ignoring-files
 .vagrant*
 bin
 docker/docker

AUTHORS

@@ -20,7 +20,6 @@ Antony Messerli <amesserl@rackspace.com>
 Asbjørn Enge <asbjorn@hanafjedle.net>
 Barry Allard <barry.allard@gmail.com>
 Ben Toews <mastahyeti@gmail.com>
-Ben Wiklund <ben@daisyowl.com>
 Benoit Chesneau <bchesneau@gmail.com>
 Bhiraj Butala <abhiraj.butala@gmail.com>
 Bouke Haarsma <bouke@webatoom.nl>
@@ -48,7 +47,6 @@ Daniel YC Lin <dlin.tw@gmail.com>
 Darren Coxall <darren@darrencoxall.com>
 David Calavera <david.calavera@gmail.com>
 David Sissitka <me@dsissitka.com>
-Dinesh Subhraveti <dineshs@altiscale.com>
 Deni Bertovic <deni@kset.org>
 Dominik Honnef <dominik@honnef.co>
 Don Spaulding <donspauldingii@gmail.com>
@@ -70,7 +68,6 @@ Francisco Souza <f@souza.cc>
 Frederick F. Kautz IV <fkautz@alumni.cmu.edu>
 Gabriel Monroy <gabriel@opdemand.com>
 Gareth Rushgrove <gareth@morethanseven.net>
-Graydon Hoare <graydon@pobox.com>
 Greg Thornton <xdissent@me.com>
 Guillaume J. Charmes <guillaume.charmes@dotcloud.com>
 Gurjeet Singh <gurjeet@singh.im>
@@ -116,7 +113,6 @@ Kyle Conroy <kyle.j.conroy@gmail.com>
 Laurie Voss <github@seldo.com>
 Louis Opter <kalessin@kalessin.fr>
 Manuel Meurer <manuel@krautcomputing.com>
-Manuel Woelker <docker@manuel.woelker.org>
 Marco Hennings <marco.hennings@freiheit.com>
 Marcus Farkas <toothlessgear@finitebox.com>
 Marcus Ramberg <marcus@nordaaker.com>

CHANGELOG.md

@@ -1,210 +1,5 @@
 # Changelog
 
-## 0.7.3 (2013-01-02)
-
-#### Builder
-
-+ Update ADD to use the image cache, based on a hash of the added content
-* Add error message for empty Dockerfile
-
-#### Documentation
-
-- Fix outdated link to the "Introduction" on www.docker.io
-+ Update the docs to get wider when the screen does
-- Add information about needing to install LXC when using raw binaries
-* Update Fedora documentation to disentangle the docker and docker.io conflict
-* Add a note about using the new `-mtu` flag in several GCE zones
-+ Add FrugalWare installation instructions
-+ Add a more complete example of `docker run`
-- Fix API documentation for creating and starting Privileged containers
-- Add missing "name" parameter documentation on "/containers/create"
-* Add a mention of `lxc-checkconfig` as a way to check for some of the necessary kernel configuration
-- Update the 1.8 API documentation with some additions that were added to the docs for 1.7
-
-#### Hack
-
-- Add missing libdevmapper dependency to the packagers documentation
-* Update minimum Go requirement to a hard line at Go 1.2+
-* Many minor improvements to the Vagrantfile
-+ Add ability to customize dockerinit search locations when compiling (to be used very sparingly only by packagers of platforms who require a nonstandard location)
-+ Add coverprofile generation reporting
-- Add `-a` to our Go build flags, removing the need for recompiling the stdlib manually
-* Update Dockerfile to be more canonical and have less spurious warnings during build
-- Fix some miscellaneous `docker pull` progress bar display issues
-* Migrate more miscellaneous packages under the "pkg" folder
-* Update TextMate highlighting to automatically be enabled for files named "Dockerfile"
-* Reorganize syntax highlighting files under a common "contrib/syntax" directory
-* Update install.sh script (https://get.docker.io/) to not fail if busybox fails to download or run at the end of the Ubuntu/Debian installation
-* Add support for container names in bash completion
-
-#### Packaging
-
-+ Add an official Docker client binary for Darwin (Mac OS X)
-* Remove empty "Vendor" string and added "License" on deb package
-+ Add a stubbed version of "/etc/default/docker" in the deb package
-
-#### Runtime
-
-* Update layer application to extract tars in place, avoiding file churn while handling whiteouts
-- Fix permissiveness of mtime comparisons in tar handling (since GNU tar and Go tar do not yet support sub-second mtime precision)
-* Reimplement `docker top` in pure Go to work more consistently, and even inside Docker-in-Docker (thus removing the shell injection vulnerability present in some versions of `lxc-ps`)
-+ Update `-H unix://` to work similarly to `-H tcp://` by inserting the default values for missing portions
-- Fix more edge cases regarding dockerinit and deleted or replaced docker or dockerinit files
-* Update container name validation to include '.'
-- Fix use of a symlink or non-absolute path as the argument to `-g` to work as expected
-* Update to handle external mounts outside of LXC, fixing many small mounting quirks and making future execution backends and other features simpler
-* Update to use proper box-drawing characters everywhere in `docker images -tree`
-* Move MTU setting from LXC configuration to directly use netlink
-* Add `-S` option to external tar invocation for more efficient spare file handling
-+ Add arch/os info to User-Agent string, especially for registry requests
-+ Add `-mtu` option to Docker daemon for configuring MTU
-- Fix `docker build` to exit with a non-zero exit code on error
-+ Add `DOCKER_HOST` environment variable to configure the client `-H` flag without specifying it manually for every invocation
-
-## 0.7.2 (2013-12-16)
-
-#### Runtime
-
-+ Validate container names on creation with standard regex
-* Increase maximum image depth to 127 from 42
-* Continue to move api endpoints to the job api
-+ Add -bip flag to allow specification of dynamic bridge IP via CIDR
-- Allow bridge creation when ipv6 is not enabled on certain systems
-* Set hostname and IP address from within dockerinit
-* Drop capabilities from within dockerinit
-- Fix volumes on host when symlink is present the image
-- Prevent deletion of image if ANY container is depending on it even if the container is not running
-* Update docker push to use new progress display
-* Use os.Lstat to allow mounting unix sockets when inspecting volumes
-- Adjust handling of inactive user login
-- Add missing defines in devicemapper for older kernels
-- Allow untag operations with no container validation
-- Add auth config to docker build
-
-#### Documentation
-
-* Add more information about Docker logging
-+ Add RHEL documentation
-* Add a direct example for changing the CMD that is run in a container
-* Update Arch installation documentation
-+ Add section on Trusted Builds
-+ Add Network documentation page
-
-#### Other
-
-+ Add new cover bundle for providing code coverage reporting
-* Separate integration tests in bundles
-* Make Tianon the hack maintainer
-* Update mkimage-debootstrap with more tweaks for keeping images small
-* Use https to get the install script
-* Remove vendored dotcloud/tar now that Go 1.2 has been released
-
-## 0.7.1 (2013-12-05)
-
-#### Documentation
-
-+ Add @SvenDowideit as documentation maintainer
-+ Add links example
-+ Add documentation regarding ambassador pattern
-+ Add Google Cloud Platform docs
-+ Add dockerfile best practices
-* Update doc for RHEL
-* Update doc for registry
-* Update Postgres examples
-* Update doc for Ubuntu install
-* Improve remote api doc
-
-#### Runtime
-
-+ Add hostconfig to docker inspect
-+ Implement `docker log -f` to stream logs
-+ Add env variable to disable kernel version warning
-+ Add -format to `docker inspect`
-+ Support bind-mount for files
-- Fix bridge creation on RHEL
-- Fix image size calculation
-- Make sure iptables are called even if the bridge already exists
-- Fix issue with stderr only attach
-- Remove init layer when destroying a container
-- Fix same port binding on different interfaces
-- `docker build` now returns the correct exit code
-- Fix `docker port` to display correct port
-- `docker build` now check that the dockerfile exists client side
-- `docker attach` now returns the correct exit code
-- Remove the name entry when the container does not exist
-
-#### Registry
-
-* Improve progress bars, add ETA for downloads
-* Simultaneous pulls now waits for the first to finish instead of failing
-- Tag only the top-layer image when pushing to registry
-- Fix issue with offline image transfer
-- Fix issue preventing using ':' in password for registry
-
-#### Other
-
-+ Add pprof handler for debug
-+ Create a Makefile
-* Use stdlib tar that now includes fix
-* Improve make.sh test script
-* Handle SIGQUIT on the daemon
-* Disable verbose during tests
-* Upgrade to go1.2 for official build
-* Improve unit tests
-* The test suite now runs all tests even if one fails
-* Refactor C in Go (Devmapper)
-- Fix OSX compilation
-
-## 0.7.0 (2013-11-25)
-
-#### Notable features since 0.6.0
-
-* Storage drivers: choose from aufs, device-mapper, or vfs.
-* Standard Linux support: docker now runs on unmodified Linux kernels and all major distributions.
-* Links: compose complex software stacks by connecting containers to each other.
-* Container naming: organize your containers by giving them memorable names.
-* Advanced port redirects: specify port redirects per interface, or keep sensitive ports private.
-* Offline transfer: push and pull images to the filesystem without losing information.
-* Quality: numerous bugfixes and small usability improvements. Significant increase in test coverage.
-
-## 0.6.7 (2013-11-21)
-
-#### Runtime
-
-* Improve stability, fixes some race conditons
-* Skip the volumes mounted when deleting the volumes of container.
-* Fix layer size computation: handle hard links correctly
-* Use the work Path for docker cp CONTAINER:PATH
-* Fix tmp dir never cleanup
-* Speedup docker ps
-* More informative error message on name collisions
-* Fix nameserver regex
-* Always return long id's
-* Fix container restart race condition
-* Keep published ports on docker stop;docker start
-* Fix container networking on Fedora
-* Correctly express "any address" to iptables
-* Fix network setup when reconnecting to ghost container
-* Prevent deletion if image is used by a running container
-* Lock around read operations in graph
-
-#### RemoteAPI
-
-* Return full ID on docker rmi
-
-#### Client
-
-+ Add -tree option to images
-+ Offline image transfer
-* Exit with status 2 on usage error and display usage on stderr
-* Do not forward SIGCHLD to container
-* Use string timestamp for docker events -since
-
-#### Other
-
-* Update to go 1.2rc5
-+ Add /etc/default/docker support to upstart
-
 ## 0.6.6 (2013-11-06)
 
 #### Runtime
@@ -214,7 +9,7 @@
 + Add lock around write operations in graph
 * Check if port is valid
 * Fix restart runtime error with ghost container networking
-+ Add some more colors and animals to increase the pool of generated names
++ Added some more colors and animals to increase the pool of generated names
 * Fix issues in docker inspect
 + Escape apparmor confinement
 + Set environment variables using a file.
@@ -222,7 +17,6 @@
 + Prevent DNS server conflicts in CreateBridgeIface
 + Validate bind mounts on the server side
 + Use parent image config in docker build
-* Fix regression in /etc/hosts
 
 #### Client
 
@@ -368,7 +162,7 @@
 * Improve network performance for VirtualBox
 * Revamp install.sh to be usable by more people, and to use official install methods whenever possible (apt repo, portage tree, etc.)
 - Fix contrib/mkimage-debian.sh apt caching prevention
-+ Add Dockerfile.tmLanguage to contrib
++ Added Dockerfile.tmLanguage to contrib
 * Configured FPM to make /etc/init/docker.conf a config file
 * Enable SSH Agent forwarding in Vagrant VM
 * Several small tweaks/fixes for contrib/mkimage-debian.sh
@@ -482,7 +276,7 @@
 * Mount /dev/shm as a tmpfs
 - Switch from http to https for get.docker.io
 * Let userland proxy handle container-bound traffic
-* Update the Docker CLI to specify a value for the "Host" header.
+* Updated the Docker CLI to specify a value for the "Host" header.
 - Change network range to avoid conflict with EC2 DNS
 - Reduce connect and read timeout when pinging the registry
 * Parallel pull
@@ -678,7 +472,7 @@
 
 + Builder: 'docker build git://URL' fetches and builds a remote git repository
 * Runtime: 'docker ps -s' optionally prints container size
-* Tests: improved and simplified
+* Tests: Improved and simplified
 - Runtime: fix a regression introduced in 0.4.3 which caused the logs command to fail.
 - Builder: fix a regression when using ADD with single regular file.
 
@@ -693,7 +487,7 @@
 + ADD of a local file will detect tar archives and unpack them
 * ADD improvements: use tar for copy + automatically unpack local archives
 * ADD uses tar/untar for copies instead of calling 'cp -ar'
-* Fix the behavior of ADD to be (mostly) reverse-compatible, predictable and well-documented.
+* Fixed the behavior of ADD to be (mostly) reverse-compatible, predictable and well-documented.
 - Fix a bug which caused builds to fail if ADD was the first command
 * Nicer output for 'docker build'
 
@@ -738,7 +532,7 @@
 + Detect faulty DNS configuration and replace it with a public default
 + Allow docker run <name>:<id>
 + You can now specify public port (ex: -p 80:4500)
-* Improve image removal to garbage-collect unreferenced parents
+* Improved image removal to garbage-collect unreferenced parents
 
 #### Client
 
@@ -792,7 +586,7 @@
 
 #### Documentation
 
-* Improve install instructions.
+* Improved install instructions.
 
 ## 0.3.3 (2013-05-23)
 
@@ -877,7 +671,7 @@
 
 + Support for data volumes ('docker run -v=PATH')
 + Share data volumes between containers ('docker run -volumes-from')
-+ Improve documentation
++ Improved documentation
 * Upgrade to Go 1.0.3
 * Various upgrades to the dev environment for contributors
 
@@ -933,7 +727,7 @@
 - Add debian packaging
 - Documentation: installing on Arch Linux
 - Documentation: running Redis on docker
-- Fix lxc 0.9 compatibility
+- Fixed lxc 0.9 compatibility
 - Automatically load aufs module
 - Various bugfixes and stability improvements
 
@@ -968,7 +762,7 @@
 - Stabilize process management
 - Layers can include a commit message
 - Simplified 'docker attach'
-- Fix support for re-attaching
+- Fixed support for re-attaching
 - Various bugfixes and stability improvements
 - Auto-download at run
 - Auto-login on push

CONTRIBUTING.md

@@ -4,13 +4,6 @@ Want to hack on Docker? Awesome! Here are instructions to get you
 started. They are probably not perfect, please let us know if anything
 feels wrong or incomplete.
 
-## Reporting Issues
-
-When reporting [issues](https://github.com/dotcloud/docker/issues) 
-on Github please include your host OS ( Ubuntu 12.04, Fedora 19, etc... )
-and the output of `docker version` along with the output of `docker info` if possible.  
-This information will help us review and fix your issue faster.
-
 ## Build Environment
 
 For instructions on setting up your development environment, please
@@ -71,7 +64,7 @@ your branch before submitting a pull request.
 
 Update the documentation when creating or modifying features. Test
 your documentation changes for clarity, concision, and correctness, as
-well as a clean documentation build. See ``docs/README.md`` for more
+well as a clean docmuent build. See ``docs/README.md`` for more
 information on building the docs and how docs get released.
 
 Write clean code. Universally formatted code promotes ease of writing, reading,
@@ -122,7 +115,6 @@ For more details see [MAINTAINERS.md](hack/MAINTAINERS.md)
 * Step 1: learn the component inside out
 * Step 2: make yourself useful by contributing code, bugfixes, support etc.
 * Step 3: volunteer on the irc channel (#docker@freenode)
-* Step 4: propose yourself at a scheduled #docker-meeting
 
 Don't forget: being a maintainer is a time investment. Make sure you will have time to make yourself available.
 You don't have to be a maintainer to make a difference on the project!

Dockerfile

@@ -24,64 +24,52 @@
 #
 
 docker-version	0.6.1
-FROM	stackbrew/ubuntu:12.04
-MAINTAINER	Tianon Gravi <admwiggin@gmail.com> (@tianon)
+from	ubuntu:12.04
+maintainer	Solomon Hykes <solomon@dotcloud.com>
 
-# Add precise-backports to get s3cmd >= 1.1.0 (so we get ENV variable support in our .s3cfg)
-RUN	echo 'deb http://archive.ubuntu.com/ubuntu precise-backports main universe' > /etc/apt/sources.list.d/backports.list
+# Build dependencies
+run	echo 'deb http://archive.ubuntu.com/ubuntu precise main universe' > /etc/apt/sources.list
+run	apt-get update
+run	apt-get install -y -q curl
+run	apt-get install -y -q git
+run	apt-get install -y -q mercurial
+run	apt-get install -y -q build-essential libsqlite3-dev
 
-# Packaged dependencies
-RUN	apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -yq \
-	apt-utils \
-	aufs-tools \
-	build-essential \
-	curl \
-	dpkg-sig \
-	git \
-	iptables \
-	libsqlite3-dev \
-	lxc \
-	mercurial \
-	reprepro \
-	ruby1.9.1 \
-	ruby1.9.1-dev \
-	s3cmd=1.1.0* \
-	--no-install-recommends
+# Install Go
+run	curl -s https://go.googlecode.com/files/go1.2rc5.src.tar.gz | tar -v -C /usr/local -xz
+env	PATH	/usr/local/go/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin
+env	GOPATH	/go:/go/src/github.com/dotcloud/docker/vendor
+run	cd /usr/local/go/src && ./make.bash && go install -ldflags '-w -linkmode external -extldflags "-static -Wl,--unresolved-symbols=ignore-in-shared-libs"' -tags netgo -a std
+
+# Ubuntu stuff
+run	apt-get install -y -q ruby1.9.3 rubygems libffi-dev
+run	gem install --no-rdoc --no-ri fpm
+run	apt-get install -y -q reprepro dpkg-sig
+
+run	apt-get install -y -q python-pip
+run	pip install s3cmd==1.1.0-beta3
+run	pip install python-magic==0.4.6
+run	/bin/echo -e '[default]\naccess_key=$AWS_ACCESS_KEY\nsecret_key=$AWS_SECRET_KEY\n' > /.s3cfg
+
+# Runtime dependencies
+run	apt-get install -y -q iptables
+run	apt-get install -y -q lxc
+run	apt-get install -y -q aufs-tools
 
 # Get lvm2 source for compiling statically
-RUN	git clone https://git.fedorahosted.org/git/lvm2.git /usr/local/lvm2 && cd /usr/local/lvm2 && git checkout -q v2_02_103
+run	git clone git://git.fedorahosted.org/git/lvm2.git /usr/local/lvm2 && cd /usr/local/lvm2 && git checkout v2_02_103
 # see https://git.fedorahosted.org/cgit/lvm2.git/refs/tags for release tags
 # note: we can't use "git clone -b" above because it requires at least git 1.7.10 to be able to use that on a tag instead of a branch and we only have 1.7.9.5
 
 # Compile and install lvm2
-RUN	cd /usr/local/lvm2 && ./configure --enable-static_link && make device-mapper && make install_device-mapper
+run	cd /usr/local/lvm2 && ./configure --enable-static_link && make device-mapper && make install_device-mapper
 # see https://git.fedorahosted.org/cgit/lvm2.git/tree/INSTALL
 
-# Install Go
-RUN	curl -s https://go.googlecode.com/files/go1.2.src.tar.gz | tar -v -C /usr/local -xz
-ENV	PATH	/usr/local/go/bin:$PATH
-ENV	GOPATH	/go:/go/src/github.com/dotcloud/docker/vendor
-RUN	cd /usr/local/go/src && ./make.bash --no-clean 2>&1
-
-# Compile Go for cross compilation
-ENV	DOCKER_CROSSPLATFORMS	darwin/amd64 darwin/386
-# TODO add linux/386 and linux/arm
-RUN	cd /usr/local/go/src && bash -xc 'for platform in $DOCKER_CROSSPLATFORMS; do GOOS=${platform%/*} GOARCH=${platform##*/} ./make.bash --no-clean 2>&1; done'
-
-# Grab Go's cover tool for dead-simple code coverage testing
-RUN	go get code.google.com/p/go.tools/cmd/cover
-
-# TODO replace FPM with some very minimal debhelper stuff
-RUN	gem install --no-rdoc --no-ri fpm --version 1.0.1
-
-# Setup s3cmd config
-RUN	/bin/echo -e '[default]\naccess_key=$AWS_ACCESS_KEY\nsecret_key=$AWS_SECRET_KEY' > /.s3cfg
-
-VOLUME	/var/lib/docker
-WORKDIR	/go/src/github.com/dotcloud/docker
+volume	/var/lib/docker
+workdir	/go/src/github.com/dotcloud/docker
 
 # Wrap all commands in the "docker-in-docker" script to allow nested containers
-ENTRYPOINT	["hack/dind"]
+entrypoint	["hack/dind"]
 
 # Upload docker source
-ADD	.	/go/src/github.com/dotcloud/docker
+add	.	/go/src/github.com/dotcloud/docker

MAINTAINERS

@@ -3,6 +3,4 @@ Guillaume Charmes <guillaume@dotcloud.com> (@creack)
 Victor Vieux <victor@dotcloud.com> (@vieux)
 Michael Crosby <michael@crosbymichael.com> (@crosbymichael)
 api.go: Victor Vieux <victor@dotcloud.com> (@vieux)
-Dockerfile: Tianon Gravi <admwiggin@gmail.com> (@tianon)
-Makefile: Tianon Gravi <admwiggin@gmail.com> (@tianon)
 Vagrantfile: Daniel Mizyrycki <daniel@dotcloud.com> (@mzdaniel)

Makefile

@@ -1,29 +0,0 @@
-.PHONY: all binary build cross default docs shell test
-
-DOCKER_RUN_DOCKER := docker run -rm -i -t -privileged -e TESTFLAGS -v $(CURDIR)/bundles:/go/src/github.com/dotcloud/docker/bundles docker
-
-default: binary
-
-all: build
-	$(DOCKER_RUN_DOCKER) hack/make.sh
-
-binary: build
-	$(DOCKER_RUN_DOCKER) hack/make.sh binary
-
-cross: build
-	$(DOCKER_RUN_DOCKER) hack/make.sh binary cross
-
-docs:
-	docker build -t docker-docs docs && docker run -p 8000:8000 docker-docs
-
-test: build
-	$(DOCKER_RUN_DOCKER) hack/make.sh test test-integration
-
-shell: build
-	$(DOCKER_RUN_DOCKER) bash
-
-build: bundles
-	docker build -t docker .
-
-bundles:
-	mkdir bundles

VERSION

@@ -1 +1 @@
-0.7.3
+0.7.0-rc7

Vagrantfile

@@ -26,7 +26,7 @@ fi
 # Adding an apt gpg key is idempotent.
 wget -q -O - https://get.docker.io/gpg | apt-key add -
 
-# Creating the docker.list file is idempotent, but it may overwrite desired
+# Creating the docker.list file is idempotent, but it may overrite desired
 # settings if it already exists.  This could be solved with md5sum but it
 # doesn't seem worth it.
 echo 'deb http://get.docker.io/ubuntu docker main' > \
@@ -41,7 +41,7 @@ apt-get install -q -y lxc-docker
 usermod -a -G docker "$user"
 
 tmp=`mktemp -q` && {
-    # Only install the backport kernel, don't bother upgrading if the backport is
+    # Only install the backport kernel, don't bother upgrade if the backport is
     # already installed.  We want parse the output of apt so we need to save it
     # with 'tee'.  NOTE: The installation of the kernel will trigger dkms to
     # install vboxguest if needed.
@@ -70,7 +70,7 @@ SCRIPT
 # trigger dkms to build the virtualbox guest module install.
 $vbox_script = <<VBOX_SCRIPT + $script
 # Install the VirtualBox guest additions if they aren't already installed.
-if [ ! -d /opt/VBoxGuestAdditions-4.3.4/ ]; then
+if [ ! -d /opt/VBoxGuestAdditions-4.3.2/ ]; then
     # Update remote package metadata.  'apt-get update' is idempotent.
     apt-get update -q
 
@@ -79,10 +79,9 @@ if [ ! -d /opt/VBoxGuestAdditions-4.3.4/ ]; then
     apt-get install -q -y linux-headers-generic-lts-raring dkms
 
     echo 'Downloading VBox Guest Additions...'
-    wget -cq http://dlc.sun.com.edgesuite.net/virtualbox/4.3.4/VBoxGuestAdditions_4.3.4.iso
-    echo "f120793fa35050a8280eacf9c930cf8d9b88795161520f6515c0cc5edda2fe8a  VBoxGuestAdditions_4.3.4.iso" | sha256sum --check || exit 1
+    wget -cq http://dlc.sun.com.edgesuite.net/virtualbox/4.3.2/VBoxGuestAdditions_4.3.2.iso
 
-    mount -o loop,ro /home/vagrant/VBoxGuestAdditions_4.3.4.iso /mnt
+    mount -o loop,ro /home/vagrant/VBoxGuestAdditions_4.3.2.iso /mnt
     /mnt/VBoxLinuxAdditions.run --nox11
     umount /mnt
 fi

api.go

@@ -1,16 +1,12 @@
 package docker
 
 import (
-	"bufio"
-	"bytes"
 	"code.google.com/p/go.net/websocket"
 	"encoding/base64"
 	"encoding/json"
-	"expvar"
 	"fmt"
 	"github.com/dotcloud/docker/archive"
 	"github.com/dotcloud/docker/auth"
-	"github.com/dotcloud/docker/pkg/systemd"
 	"github.com/dotcloud/docker/utils"
 	"github.com/gorilla/mux"
 	"io"
@@ -19,7 +15,6 @@ import (
 	"mime"
 	"net"
 	"net/http"
-	"net/http/pprof"
 	"os"
 	"os/exec"
 	"regexp"
@@ -28,7 +23,7 @@ import (
 )
 
 const (
-	APIVERSION        = 1.8
+	APIVERSION        = 1.7
 	DEFAULTHTTPHOST   = "127.0.0.1"
 	DEFAULTHTTPPORT   = 4243
 	DEFAULTUNIXSOCKET = "/var/run/docker.sock"
@@ -140,8 +135,7 @@ func postAuth(srv *Server, version float64, w http.ResponseWriter, r *http.Reque
 }
 
 func getVersion(srv *Server, version float64, w http.ResponseWriter, r *http.Request, vars map[string]string) error {
-	srv.Eng.ServeHTTP(w, r)
-	return nil
+	return writeJSON(w, http.StatusOK, srv.DockerVersion())
 }
 
 func postContainersKill(srv *Server, version float64, w http.ResponseWriter, r *http.Request, vars map[string]string) error {
@@ -151,11 +145,19 @@ func postContainersKill(srv *Server, version float64, w http.ResponseWriter, r *
 	if err := parseForm(r); err != nil {
 		return err
 	}
-	job := srv.Eng.Job("kill", vars["name"])
-	if sig := r.Form.Get("signal"); sig != "" {
-		job.Args = append(job.Args, sig)
+	name := vars["name"]
+
+	signal := 0
+	if r != nil {
+		if s := r.Form.Get("signal"); s != "" {
+			s, err := strconv.Atoi(s)
+			if err != nil {
+				return err
+			}
+			signal = s
+		}
 	}
-	if err := job.Run(); err != nil {
+	if err := srv.ContainerKill(name, signal); err != nil {
 		return err
 	}
 	w.WriteHeader(http.StatusNoContent)
@@ -166,11 +168,10 @@ func getContainersExport(srv *Server, version float64, w http.ResponseWriter, r
 	if vars == nil {
 		return fmt.Errorf("Missing parameter")
 	}
-	job := srv.Eng.Job("export", vars["name"])
-	if err := job.Stdout.Add(w); err != nil {
-		return err
-	}
-	if err := job.Run(); err != nil {
+	name := vars["name"]
+
+	if err := srv.ContainerExport(name, w); err != nil {
+		utils.Errorf("%s", err)
 		return err
 	}
 	return nil
@@ -216,8 +217,7 @@ func getImagesViz(srv *Server, version float64, w http.ResponseWriter, r *http.R
 }
 
 func getInfo(srv *Server, version float64, w http.ResponseWriter, r *http.Request, vars map[string]string) error {
-	srv.Eng.ServeHTTP(w, r)
-	return nil
+	return writeJSON(w, http.StatusOK, srv.DockerInfo())
 }
 
 func getEvents(srv *Server, version float64, w http.ResponseWriter, r *http.Request, vars map[string]string) error {
@@ -254,7 +254,7 @@ func getEvents(srv *Server, version float64, w http.ResponseWriter, r *http.Requ
 	wf.Flush()
 	if since != 0 {
 		// If since, send previous events that happened after the timestamp
-		for _, event := range srv.GetEvents() {
+		for _, event := range srv.events {
 			if event.Time >= since {
 				err := sendEvent(wf, &event)
 				if err != nil && err.Error() == "JSON error" {
@@ -357,13 +357,18 @@ func postImagesTag(srv *Server, version float64, w http.ResponseWriter, r *http.
 	if err := parseForm(r); err != nil {
 		return err
 	}
+	repo := r.Form.Get("repo")
+	tag := r.Form.Get("tag")
 	if vars == nil {
 		return fmt.Errorf("Missing parameter")
 	}
+	name := vars["name"]
+	force, err := getBoolParam(r.Form.Get("force"))
+	if err != nil {
+		return err
+	}
 
-	job := srv.Eng.Job("tag", vars["name"], r.Form.Get("repo"), r.Form.Get("tag"))
-	job.Setenv("force", r.Form.Get("force"))
-	if err := job.Run(); err != nil {
+	if err := srv.ContainerTag(name, repo, tag, force); err != nil {
 		return err
 	}
 	w.WriteHeader(http.StatusCreated)
@@ -378,17 +383,13 @@ func postCommit(srv *Server, version float64, w http.ResponseWriter, r *http.Req
 	if err := json.NewDecoder(r.Body).Decode(config); err != nil && err != io.EOF {
 		utils.Errorf("%s", err)
 	}
-
-	job := srv.Eng.Job("commit", r.Form.Get("container"))
-	job.Setenv("repo", r.Form.Get("repo"))
-	job.Setenv("tag", r.Form.Get("tag"))
-	job.Setenv("author", r.Form.Get("author"))
-	job.Setenv("comment", r.Form.Get("comment"))
-	job.SetenvJson("config", config)
-
-	var id string
-	job.Stdout.AddString(&id)
-	if err := job.Run(); err != nil {
+	repo := r.Form.Get("repo")
+	tag := r.Form.Get("tag")
+	container := r.Form.Get("container")
+	author := r.Form.Get("author")
+	comment := r.Form.Get("comment")
+	id, err := srv.ContainerCommit(container, repo, tag, author, comment, config)
+	if err != nil {
 		return err
 	}
 
@@ -563,18 +564,12 @@ func postContainersCreate(srv *Server, version float64, w http.ResponseWriter, r
 		job.SetenvList("Dns", defaultDns)
 	}
 	// Read container ID from the first line of stdout
-	job.Stdout.AddString(&out.ID)
+	job.StdoutParseString(&out.ID)
 	// Read warnings from stderr
-	warnings := &bytes.Buffer{}
-	job.Stderr.Add(warnings)
+	job.StderrParseLines(&out.Warnings, 0)
 	if err := job.Run(); err != nil {
 		return err
 	}
-	// Parse warnings from stderr
-	scanner := bufio.NewScanner(warnings)
-	for scanner.Scan() {
-		out.Warnings = append(out.Warnings, scanner.Text())
-	}
 	if job.GetenvInt("Memory") > 0 && !srv.runtime.capabilities.MemoryLimit {
 		log.Println("WARNING: Your kernel does not support memory limit capabilities. Limitation discarded.")
 		out.Warnings = append(out.Warnings, "Your kernel does not support memory limit capabilities. Limitation discarded.")
@@ -683,12 +678,17 @@ func postContainersStop(srv *Server, version float64, w http.ResponseWriter, r *
 	if err := parseForm(r); err != nil {
 		return err
 	}
+	t, err := strconv.Atoi(r.Form.Get("t"))
+	if err != nil || t < 0 {
+		t = 10
+	}
+
 	if vars == nil {
 		return fmt.Errorf("Missing parameter")
 	}
-	job := srv.Eng.Job("stop", vars["name"])
-	job.Setenv("t", r.Form.Get("t"))
-	if err := job.Run(); err != nil {
+	name := vars["name"]
+
+	if err := srv.ContainerStop(name, t); err != nil {
 		return err
 	}
 	w.WriteHeader(http.StatusNoContent)
@@ -699,28 +699,33 @@ func postContainersWait(srv *Server, version float64, w http.ResponseWriter, r *
 	if vars == nil {
 		return fmt.Errorf("Missing parameter")
 	}
-	job := srv.Eng.Job("wait", vars["name"])
-	var statusStr string
-	job.Stdout.AddString(&statusStr)
-	if err := job.Run(); err != nil {
-		return err
-	}
-	// Parse a 16-bit encoded integer to map typical unix exit status.
-	status, err := strconv.ParseInt(statusStr, 10, 16)
+	name := vars["name"]
+
+	status, err := srv.ContainerWait(name)
 	if err != nil {
 		return err
 	}
-	return writeJSON(w, http.StatusOK, &APIWait{StatusCode: int(status)})
+
+	return writeJSON(w, http.StatusOK, &APIWait{StatusCode: status})
 }
 
 func postContainersResize(srv *Server, version float64, w http.ResponseWriter, r *http.Request, vars map[string]string) error {
 	if err := parseForm(r); err != nil {
 		return err
 	}
+	height, err := strconv.Atoi(r.Form.Get("h"))
+	if err != nil {
+		return err
+	}
+	width, err := strconv.Atoi(r.Form.Get("w"))
+	if err != nil {
+		return err
+	}
 	if vars == nil {
 		return fmt.Errorf("Missing parameter")
 	}
-	if err := srv.Eng.Job("resize", vars["name"], r.Form.Get("h"), r.Form.Get("w")).Run(); err != nil {
+	name := vars["name"]
+	if err := srv.ContainerResize(name, height, width); err != nil {
 		return err
 	}
 	return nil
@@ -860,10 +865,7 @@ func getContainersByName(srv *Server, version float64, w http.ResponseWriter, r
 		return fmt.Errorf("Conflict between containers and images")
 	}
 
-	container.readHostConfig()
-	c := APIContainer{container, container.hostConfig}
-
-	return writeJSON(w, http.StatusOK, c)
+	return writeJSON(w, http.StatusOK, container)
 }
 
 func getImagesByName(srv *Server, version float64, w http.ResponseWriter, r *http.Request, vars map[string]string) error {
@@ -889,25 +891,12 @@ func postBuild(srv *Server, version float64, w http.ResponseWriter, r *http.Requ
 	if version < 1.3 {
 		return fmt.Errorf("Multipart upload for build is no longer supported. Please upgrade your docker client.")
 	}
-	var (
-		remoteURL         = r.FormValue("remote")
-		repoName          = r.FormValue("t")
-		rawSuppressOutput = r.FormValue("q")
-		rawNoCache        = r.FormValue("nocache")
-		rawRm             = r.FormValue("rm")
-		authEncoded       = r.Header.Get("X-Registry-Auth")
-		authConfig        = &auth.AuthConfig{}
-		tag               string
-	)
-	repoName, tag = utils.ParseRepositoryTag(repoName)
-	if authEncoded != "" {
-		authJson := base64.NewDecoder(base64.URLEncoding, strings.NewReader(authEncoded))
-		if err := json.NewDecoder(authJson).Decode(authConfig); err != nil {
-			// for a pull it is not an error if no auth was given
-			// to increase compatibility with the existing api it is defaulting to be empty
-			authConfig = &auth.AuthConfig{}
-		}
-	}
+	remoteURL := r.FormValue("remote")
+	repoName := r.FormValue("t")
+	rawSuppressOutput := r.FormValue("q")
+	rawNoCache := r.FormValue("nocache")
+	rawRm := r.FormValue("rm")
+	repoName, tag := utils.ParseRepositoryTag(repoName)
 
 	var context io.Reader
 
@@ -933,7 +922,7 @@ func postBuild(srv *Server, version float64, w http.ResponseWriter, r *http.Requ
 		}
 		context = c
 	} else if utils.IsURL(remoteURL) {
-		f, err := utils.Download(remoteURL)
+		f, err := utils.Download(remoteURL, ioutil.Discard)
 		if err != nil {
 			return err
 		}
@@ -962,26 +951,9 @@ func postBuild(srv *Server, version float64, w http.ResponseWriter, r *http.Requ
 		return err
 	}
 
-	if version >= 1.8 {
-		w.Header().Set("Content-Type", "application/json")
-	}
-	sf := utils.NewStreamFormatter(version >= 1.8)
-	b := NewBuildFile(srv,
-		&StdoutFormater{
-			Writer:          utils.NewWriteFlusher(w),
-			StreamFormatter: sf,
-		},
-		&StderrFormater{
-			Writer:          utils.NewWriteFlusher(w),
-			StreamFormatter: sf,
-		},
-		!suppressOutput, !noCache, rm, utils.NewWriteFlusher(w), sf, authConfig)
+	b := NewBuildFile(srv, utils.NewWriteFlusher(w), !suppressOutput, !noCache, rm)
 	id, err := b.Build(context)
 	if err != nil {
-		if sf.Used() {
-			w.Write(sf.FormatError(err))
-			return nil
-		}
 		return fmt.Errorf("Error build: %s", err)
 	}
 	if repoName != "" {
@@ -1065,37 +1037,9 @@ func makeHttpHandler(srv *Server, logging bool, localMethod string, localRoute s
 	}
 }
 
-// Replicated from expvar.go as not public.
-func expvarHandler(w http.ResponseWriter, r *http.Request) {
-	w.Header().Set("Content-Type", "application/json; charset=utf-8")
-	fmt.Fprintf(w, "{\n")
-	first := true
-	expvar.Do(func(kv expvar.KeyValue) {
-		if !first {
-			fmt.Fprintf(w, ",\n")
-		}
-		first = false
-		fmt.Fprintf(w, "%q: %s", kv.Key, kv.Value)
-	})
-	fmt.Fprintf(w, "\n}\n")
-}
-
-func AttachProfiler(router *mux.Router) {
-	router.HandleFunc("/debug/vars", expvarHandler)
-	router.HandleFunc("/debug/pprof/", pprof.Index)
-	router.HandleFunc("/debug/pprof/cmdline", pprof.Cmdline)
-	router.HandleFunc("/debug/pprof/profile", pprof.Profile)
-	router.HandleFunc("/debug/pprof/symbol", pprof.Symbol)
-	router.HandleFunc("/debug/pprof/heap", pprof.Handler("heap").ServeHTTP)
-	router.HandleFunc("/debug/pprof/goroutine", pprof.Handler("goroutine").ServeHTTP)
-	router.HandleFunc("/debug/pprof/threadcreate", pprof.Handler("threadcreate").ServeHTTP)
-}
-
 func createRouter(srv *Server, logging bool) (*mux.Router, error) {
 	r := mux.NewRouter()
-	if os.Getenv("DEBUG") != "" {
-		AttachProfiler(r)
-	}
+
 	m := map[string]map[string]HttpApiFunc{
 		"GET": {
 			"/events":                         getEvents,
@@ -1182,6 +1126,8 @@ func ServeRequest(srv *Server, apiversion float64, w http.ResponseWriter, req *h
 }
 
 func ListenAndServe(proto, addr string, srv *Server, logging bool) error {
+	log.Printf("Listening for HTTP on %s (%s)\n", addr, proto)
+
 	r, err := createRouter(srv, logging)
 	if err != nil {
 		return err
@@ -1212,9 +1158,5 @@ func ListenAndServe(proto, addr string, srv *Server, logging bool) error {
 		}
 	}
 	httpSrv := http.Server{Addr: addr, Handler: r}
-
-	log.Printf("Listening for HTTP on %s (%s)\n", addr, proto)
-	// Tell the init daemon we are accepting requests
-	go systemd.SdNotify("READY=1")
 	return httpSrv.Serve(l)
 }

api_params.go

@@ -29,6 +29,23 @@ type (
 		VirtualSize int64
 	}
 
+	APIInfo struct {
+		Debug              bool
+		Containers         int
+		Images             int
+		Driver             string      `json:",omitempty"`
+		DriverStatus       [][2]string `json:",omitempty"`
+		NFd                int         `json:",omitempty"`
+		NGoroutines        int         `json:",omitempty"`
+		MemoryLimit        bool        `json:",omitempty"`
+		SwapLimit          bool        `json:",omitempty"`
+		IPv4Forwarding     bool        `json:",omitempty"`
+		LXCVersion         string      `json:",omitempty"`
+		NEventsListener    int         `json:",omitempty"`
+		KernelVersion      string      `json:",omitempty"`
+		IndexServerAddress string      `json:",omitempty"`
+	}
+
 	APITop struct {
 		Titles    []string
 		Processes [][]string
@@ -78,6 +95,12 @@ type (
 		IP          string
 	}
 
+	APIVersion struct {
+		Version   string
+		GitCommit string `json:",omitempty"`
+		GoVersion string `json:",omitempty"`
+	}
+
 	APIWait struct {
 		StatusCode int
 	}
@@ -95,10 +118,6 @@ type (
 		Resource string
 		HostPath string
 	}
-	APIContainer struct {
-		*Container
-		HostConfig *HostConfig
-	}
 )
 
 func (api APIImages) ToLegacy() []APIImagesOld {

archive/archive.go

@@ -3,8 +3,6 @@ package archive
 import (
 	"archive/tar"
 	"bytes"
-	"compress/gzip"
-	"compress/bzip2"
 	"fmt"
 	"github.com/dotcloud/docker/utils"
 	"io"
@@ -61,43 +59,6 @@ func DetectCompression(source []byte) Compression {
 	return Uncompressed
 }
 
-func xzDecompress(archive io.Reader) (io.Reader, error) {
-	args := []string{"xz", "-d", "-c", "-q"}
-
-	return CmdStream(exec.Command(args[0], args[1:]...), archive, nil)
-}
-
-func DecompressStream(archive io.Reader) (io.Reader, error) {
-	buf := make([]byte, 10)
-	totalN := 0
-	for totalN < 10 {
-		n, err := archive.Read(buf[totalN:])
-		if err != nil {
-			if err == io.EOF {
-				return nil, fmt.Errorf("Tarball too short")
-			}
-			return nil, err
-		}
-		totalN += n
-		utils.Debugf("[tar autodetect] n: %d", n)
-	}
-	compression := DetectCompression(buf)
-	wrap := io.MultiReader(bytes.NewReader(buf), archive)
-
-	switch compression {
-	case Uncompressed:
-		return wrap, nil
-	case Gzip:
-		return gzip.NewReader(wrap)
-	case Bzip2:
-		return bzip2.NewReader(wrap), nil
-	case Xz:
-		return xzDecompress(wrap)
-	default:
-		return nil, fmt.Errorf("Unsupported compression format %s", (&compression).Extension())
-	}
-}
-
 func (compression *Compression) Flag() string {
 	switch *compression {
 	case Bzip2:
@@ -149,7 +110,7 @@ func escapeName(name string) string {
 // Tar creates an archive from the directory at `path`, only including files whose relative
 // paths are included in `filter`. If `filter` is nil, then all files are included.
 func TarFilter(path string, options *TarOptions) (io.Reader, error) {
-	args := []string{"tar", "-S", "--numeric-owner", "-f", "-", "-C", path, "-T", "-"}
+	args := []string{"tar", "--numeric-owner", "-f", "-", "-C", path, "-T", "-"}
 	if options.Includes == nil {
 		options.Includes = []string{"."}
 	}
@@ -194,7 +155,7 @@ func TarFilter(path string, options *TarOptions) (io.Reader, error) {
 		}
 	}
 
-	return CmdStream(exec.Command(args[0], args[1:]...), bytes.NewBufferString(files), func() {
+	return CmdStream(exec.Command(args[0], args[1:]...), &files, func() {
 		if tmpDir != "" {
 			_ = os.RemoveAll(tmpDir)
 		}
@@ -228,7 +189,7 @@ func Untar(archive io.Reader, path string, options *TarOptions) error {
 	compression := DetectCompression(buf)
 
 	utils.Debugf("Archive compression detected: %s", compression.Extension())
-	args := []string{"-S", "--numeric-owner", "-f", "-", "-C", path, "-x" + compression.Flag()}
+	args := []string{"--numeric-owner", "-f", "-", "-C", path, "-x" + compression.Flag()}
 
 	if options != nil {
 		for _, exclude := range options.Excludes {
@@ -340,7 +301,7 @@ func CopyFileWithTar(src, dst string) error {
 // CmdStream executes a command, and returns its stdout as a stream.
 // If the command fails to run or doesn't complete successfully, an error
 // will be returned, including anything written on stderr.
-func CmdStream(cmd *exec.Cmd, input io.Reader, atEnd func()) (io.Reader, error) {
+func CmdStream(cmd *exec.Cmd, input *string, atEnd func()) (io.Reader, error) {
 	if input != nil {
 		stdin, err := cmd.StdinPipe()
 		if err != nil {
@@ -351,7 +312,7 @@ func CmdStream(cmd *exec.Cmd, input io.Reader, atEnd func()) (io.Reader, error)
 		}
 		// Write stdin if any
 		go func() {
-			io.Copy(stdin, input)
+			_, _ = stdin.Write([]byte(*input))
 			stdin.Close()
 		}()
 	}

archive/changes.go

@@ -6,7 +6,6 @@ import (
 	"path/filepath"
 	"strings"
 	"syscall"
-	"time"
 )
 
 type ChangeType int
@@ -35,21 +34,6 @@ func (change *Change) String() string {
 	return fmt.Sprintf("%s %s", kind, change.Path)
 }
 
-// Gnu tar and the go tar writer don't have sub-second mtime
-// precision, which is problematic when we apply changes via tar
-// files, we handle this by comparing for exact times, *or* same
-// second count and either a or b having exactly 0 nanoseconds
-func sameFsTime(a, b time.Time) bool {
-	return a == b ||
-		(a.Unix() == b.Unix() &&
-			(a.Nanosecond() == 0 || b.Nanosecond() == 0))
-}
-
-func sameFsTimeSpec(a, b syscall.Timespec) bool {
-	return a.Sec == b.Sec &&
-		(a.Nsec == b.Nsec || a.Nsec == 0 || b.Nsec == 0)
-}
-
 func Changes(layers []string, rw string) ([]Change, error) {
 	var changes []Change
 	err := filepath.Walk(rw, func(path string, f os.FileInfo, err error) error {
@@ -101,7 +85,7 @@ func Changes(layers []string, rw string) ([]Change, error) {
 					// However, if it's a directory, maybe it wasn't actually modified.
 					// If you modify /foo/bar/baz, then /foo will be part of the changed files only because it's the parent of bar
 					if stat.IsDir() && f.IsDir() {
-						if f.Size() == stat.Size() && f.Mode() == stat.Mode() && sameFsTime(f.ModTime(), stat.ModTime()) {
+						if f.Size() == stat.Size() && f.Mode() == stat.Mode() && f.ModTime() == stat.ModTime() {
 							// Both directories are the same, don't record the change
 							return nil
 						}
@@ -197,7 +181,7 @@ func (info *FileInfo) addChanges(oldInfo *FileInfo, changes *[]Change) {
 				oldStat.Rdev != newStat.Rdev ||
 				// Don't look at size for dirs, its not a good measure of change
 				(oldStat.Size != newStat.Size && oldStat.Mode&syscall.S_IFDIR != syscall.S_IFDIR) ||
-				!sameFsTimeSpec(getLastModification(oldStat), getLastModification(newStat)) {
+				oldStat.Mtim != newStat.Mtim {
 				change := Change{
 					Path: newChild.path(),
 					Kind: ChangeModify,

archive/changes_test.go

@@ -71,27 +71,17 @@ func createSampleDir(t *testing.T, root string) {
 		{Symlink, "symlink1", "target1", 0666},
 		{Symlink, "symlink2", "target2", 0666},
 	}
-
-	now := time.Now()
 	for _, info := range files {
-		p := path.Join(root, info.path)
 		if info.filetype == Dir {
-			if err := os.MkdirAll(p, info.permissions); err != nil {
+			if err := os.MkdirAll(path.Join(root, info.path), info.permissions); err != nil {
 				t.Fatal(err)
 			}
 		} else if info.filetype == Regular {
-			if err := ioutil.WriteFile(p, []byte(info.contents), info.permissions); err != nil {
+			if err := ioutil.WriteFile(path.Join(root, info.path), []byte(info.contents), info.permissions); err != nil {
 				t.Fatal(err)
 			}
 		} else if info.filetype == Symlink {
-			if err := os.Symlink(info.contents, p); err != nil {
-				t.Fatal(err)
-			}
-		}
-
-		if info.filetype != Symlink {
-			// Set a consistent ctime, atime for all files and dirs
-			if err := os.Chtimes(p, now, now); err != nil {
+			if err := os.Symlink(info.contents, path.Join(root, info.path)); err != nil {
 				t.Fatal(err)
 			}
 		}
@@ -210,9 +200,6 @@ func TestChangesDirsMutated(t *testing.T) {
 	if err := copyDir(src, dst); err != nil {
 		t.Fatal(err)
 	}
-	defer os.RemoveAll(src)
-	defer os.RemoveAll(dst)
-
 	mutateSampleDir(t, dst)
 
 	changes, err := ChangesDirs(dst, src)
@@ -238,7 +225,8 @@ func TestChangesDirsMutated(t *testing.T) {
 		{"/symlinknew", ChangeAdd},
 	}
 
-	for i := 0; i < max(len(changes), len(expectedChanges)); i++ {
+	i := 0
+	for ; i < max(len(changes), len(expectedChanges)); i++ {
 		if i >= len(expectedChanges) {
 			t.Fatalf("unexpected change %s\n", changes[i].String())
 		}
@@ -247,29 +235,35 @@ func TestChangesDirsMutated(t *testing.T) {
 		}
 		if changes[i].Path == expectedChanges[i].Path {
 			if changes[i] != expectedChanges[i] {
-				t.Fatalf("Wrong change for %s, expected %s, got %s\n", changes[i].Path, changes[i].String(), expectedChanges[i].String())
+				t.Fatalf("Wrong change for %s, expected %s, got %d\n", changes[i].Path, changes[i].String(), expectedChanges[i].String())
 			}
 		} else if changes[i].Path < expectedChanges[i].Path {
 			t.Fatalf("unexpected change %s\n", changes[i].String())
 		} else {
-			t.Fatalf("no change for expected change %s != %s\n", expectedChanges[i].String(), changes[i].String())
+			t.Fatalf("no change for expected change %s\n", expectedChanges[i].String())
 		}
 	}
+	for ; i < len(expectedChanges); i++ {
+	}
+
+	os.RemoveAll(src)
+	os.RemoveAll(dst)
 }
 
 func TestApplyLayer(t *testing.T) {
+	t.Skip("Skipping TestApplyLayer due to known failures") // Disable this for now as it is broken
+	return
+
 	src, err := ioutil.TempDir("", "docker-changes-test")
 	if err != nil {
 		t.Fatal(err)
 	}
 	createSampleDir(t, src)
-	defer os.RemoveAll(src)
 	dst := src + "-copy"
 	if err := copyDir(src, dst); err != nil {
 		t.Fatal(err)
 	}
 	mutateSampleDir(t, dst)
-	defer os.RemoveAll(dst)
 
 	changes, err := ChangesDirs(dst, src)
 	if err != nil {
@@ -296,6 +290,9 @@ func TestApplyLayer(t *testing.T) {
 	}
 
 	if len(changes2) != 0 {
-		t.Fatalf("Unexpected differences after reapplying mutation: %v", changes2)
+		t.Fatalf("Unexpected differences after re applying mutation: %v", changes)
 	}
+
+	os.RemoveAll(src)
+	os.RemoveAll(dst)
 }

archive/diff.go

@@ -1,9 +1,6 @@
 package archive
 
 import (
-	"archive/tar"
-	"github.com/dotcloud/docker/utils"
-	"io"
 	"os"
 	"path/filepath"
 	"strings"
@@ -11,181 +8,85 @@ import (
 	"time"
 )
 
-// Linux device nodes are a bit weird due to backwards compat with 16 bit device nodes.
-// They are, from low to high: the lower 8 bits of the minor, then 12 bits of the major,
-// then the top 12 bits of the minor
-func mkdev(major int64, minor int64) uint32 {
-	return uint32(((minor & 0xfff00) << 12) | ((major & 0xfff) << 8) | (minor & 0xff))
-}
-func timeToTimespec(time time.Time) (ts syscall.Timespec) {
-	if time.IsZero() {
-		// Return UTIME_OMIT special value
-		ts.Sec = 0
-		ts.Nsec = ((1 << 30) - 2)
-		return
-	}
-	return syscall.NsecToTimespec(time.UnixNano())
-}
-
 // ApplyLayer parses a diff in the standard layer format from `layer`, and
 // applies it to the directory `dest`.
 func ApplyLayer(dest string, layer Archive) error {
-	// We need to be able to set any perms
-	oldmask := syscall.Umask(0)
-	defer syscall.Umask(oldmask)
+	// Poor man's diff applyer in 2 steps:
 
-	layer, err := DecompressStream(layer)
+	// Step 1: untar everything in place
+	if err := Untar(layer, dest, nil); err != nil {
+		return err
+	}
+
+	modifiedDirs := make(map[string]*syscall.Stat_t)
+	addDir := func(file string) {
+		d := filepath.Dir(file)
+		if _, exists := modifiedDirs[d]; !exists {
+			if s, err := os.Lstat(d); err == nil {
+				if sys := s.Sys(); sys != nil {
+					if stat, ok := sys.(*syscall.Stat_t); ok {
+						modifiedDirs[d] = stat
+					}
+				}
+			}
+		}
+	}
+
+	// Step 2: walk for whiteouts and apply them, removing them in the process
+	err := filepath.Walk(dest, func(fullPath string, f os.FileInfo, err error) error {
+		if err != nil {
+			if os.IsNotExist(err) {
+				// This happens in the case of whiteouts in parent dir removing a directory
+				// We just ignore it
+				return filepath.SkipDir
+			}
+			return err
+		}
+
+		// Rebase path
+		path, err := filepath.Rel(dest, fullPath)
+		if err != nil {
+			return err
+		}
+		path = filepath.Join("/", path)
+
+		// Skip AUFS metadata
+		if matched, err := filepath.Match("/.wh..wh.*", path); err != nil {
+			return err
+		} else if matched {
+			addDir(fullPath)
+			if err := os.RemoveAll(fullPath); err != nil {
+				return err
+			}
+		}
+
+		filename := filepath.Base(path)
+		if strings.HasPrefix(filename, ".wh.") {
+			rmTargetName := filename[len(".wh."):]
+			rmTargetPath := filepath.Join(filepath.Dir(fullPath), rmTargetName)
+
+			// Remove the file targeted by the whiteout
+			addDir(rmTargetPath)
+			if err := os.RemoveAll(rmTargetPath); err != nil {
+				return err
+			}
+			// Remove the whiteout itself
+			addDir(fullPath)
+			if err := os.RemoveAll(fullPath); err != nil {
+				return err
+			}
+		}
+		return nil
+	})
 	if err != nil {
 		return err
 	}
 
-	tr := tar.NewReader(layer)
+	for k, v := range modifiedDirs {
+		aTime := time.Unix(v.Atim.Unix())
+		mTime := time.Unix(v.Mtim.Unix())
 
-	var dirs []*tar.Header
-
-	// Iterate through the files in the archive.
-	for {
-		hdr, err := tr.Next()
-		if err == io.EOF {
-			// end of tar archive
-			break
-		}
-		if err != nil {
-			return err
-		}
-
-		// Normalize name, for safety and for a simple is-root check
-		hdr.Name = filepath.Clean(hdr.Name)
-
-		if !strings.HasSuffix(hdr.Name, "/") {
-			// Not the root directory, ensure that the parent directory exists.
-			// This happened in some tests where an image had a tarfile without any
-			// parent directories.
-			parent := filepath.Dir(hdr.Name)
-			parentPath := filepath.Join(dest, parent)
-			if _, err := os.Lstat(parentPath); err != nil && os.IsNotExist(err) {
-				err = os.MkdirAll(parentPath, 600)
-				if err != nil {
-					return err
-				}
-			}
-		}
-
-		// Skip AUFS metadata dirs
-		if strings.HasPrefix(hdr.Name, ".wh..wh.") {
-			continue
-		}
-
-		path := filepath.Join(dest, hdr.Name)
-		base := filepath.Base(path)
-		if strings.HasPrefix(base, ".wh.") {
-			originalBase := base[len(".wh."):]
-			originalPath := filepath.Join(filepath.Dir(path), originalBase)
-			if err := os.RemoveAll(originalPath); err != nil {
-				return err
-			}
-		} else {
-			// If path exits we almost always just want to remove and replace it.
-			// The only exception is when it is a directory *and* the file from
-			// the layer is also a directory. Then we want to merge them (i.e.
-			// just apply the metadata from the layer).
-			hasDir := false
-			if fi, err := os.Lstat(path); err == nil {
-				if fi.IsDir() && hdr.Typeflag == tar.TypeDir {
-					hasDir = true
-				} else {
-					if err := os.RemoveAll(path); err != nil {
-						return err
-					}
-				}
-			}
-
-			switch hdr.Typeflag {
-			case tar.TypeDir:
-				if !hasDir {
-					err = os.Mkdir(path, os.FileMode(hdr.Mode))
-					if err != nil {
-						return err
-					}
-				}
-				dirs = append(dirs, hdr)
-
-			case tar.TypeReg, tar.TypeRegA:
-				// Source is regular file
-				file, err := os.OpenFile(path, os.O_CREATE|os.O_WRONLY, os.FileMode(hdr.Mode))
-				if err != nil {
-					return err
-				}
-				if _, err := io.Copy(file, tr); err != nil {
-					file.Close()
-					return err
-				}
-				file.Close()
-
-			case tar.TypeBlock, tar.TypeChar, tar.TypeFifo:
-				mode := uint32(hdr.Mode & 07777)
-				switch hdr.Typeflag {
-				case tar.TypeBlock:
-					mode |= syscall.S_IFBLK
-				case tar.TypeChar:
-					mode |= syscall.S_IFCHR
-				case tar.TypeFifo:
-					mode |= syscall.S_IFIFO
-				}
-
-				if err := syscall.Mknod(path, mode, int(mkdev(hdr.Devmajor, hdr.Devminor))); err != nil {
-					return err
-				}
-
-			case tar.TypeLink:
-				if err := os.Link(filepath.Join(dest, hdr.Linkname), path); err != nil {
-					return err
-				}
-
-			case tar.TypeSymlink:
-				if err := os.Symlink(hdr.Linkname, path); err != nil {
-					return err
-				}
-
-			default:
-				utils.Debugf("unhandled type %d\n", hdr.Typeflag)
-			}
-
-			if err = syscall.Lchown(path, hdr.Uid, hdr.Gid); err != nil {
-				return err
-			}
-
-			// There is no LChmod, so ignore mode for symlink. Also, this
-			// must happen after chown, as that can modify the file mode
-			if hdr.Typeflag != tar.TypeSymlink {
-				err = syscall.Chmod(path, uint32(hdr.Mode&07777))
-				if err != nil {
-					return err
-				}
-			}
-
-			// Directories must be handled at the end to avoid further
-			// file creation in them to modify the mtime
-			if hdr.Typeflag != tar.TypeDir {
-				ts := []syscall.Timespec{timeToTimespec(hdr.AccessTime), timeToTimespec(hdr.ModTime)}
-				// syscall.UtimesNano doesn't support a NOFOLLOW flag atm, and
-				if hdr.Typeflag != tar.TypeSymlink {
-					if err := syscall.UtimesNano(path, ts); err != nil {
-						return err
-					}
-				} else {
-					if err := LUtimesNano(path, ts); err != nil {
-						return err
-					}
-				}
-			}
-		}
-	}
-
-	for _, hdr := range dirs {
-		path := filepath.Join(dest, hdr.Name)
-		ts := []syscall.Timespec{timeToTimespec(hdr.AccessTime), timeToTimespec(hdr.ModTime)}
-		if err := syscall.UtimesNano(path, ts); err != nil {
+		if err := os.Chtimes(k, aTime, mTime); err != nil {
 			return err
 		}
 	}

archive/stat_darwin.go

@@ -1,15 +0,0 @@
-package archive
-
-import "syscall"
-
-func getLastAccess(stat *syscall.Stat_t) syscall.Timespec {
-	return stat.Atimespec
-}
-
-func getLastModification(stat *syscall.Stat_t) syscall.Timespec {
-	return stat.Mtimespec
-}
-
-func LUtimesNano(path string, ts []syscall.Timespec) error {
-	return nil
-}

archive/stat_linux.go

@@ -1,32 +0,0 @@
-package archive
-
-import (
-	"syscall"
-	"unsafe"
-)
-
-func getLastAccess(stat *syscall.Stat_t) syscall.Timespec {
-	return stat.Atim
-}
-
-func getLastModification(stat *syscall.Stat_t) syscall.Timespec {
-	return stat.Mtim
-}
-
-func LUtimesNano(path string, ts []syscall.Timespec) error {
-	// These are not currently available in syscall
-	AT_FDCWD := -100
-	AT_SYMLINK_NOFOLLOW := 0x100
-
-	var _path *byte
-	_path, err := syscall.BytePtrFromString(path)
-	if err != nil {
-		return err
-	}
-
-	if _, _, err := syscall.Syscall6(syscall.SYS_UTIMENSAT, uintptr(AT_FDCWD), uintptr(unsafe.Pointer(_path)), uintptr(unsafe.Pointer(&ts[0])), uintptr(AT_SYMLINK_NOFOLLOW), 0, 0); err != 0 && err != syscall.ENOSYS {
-		return err
-	}
-
-	return nil
-}

auth/auth.go

@@ -63,7 +63,7 @@ func decodeAuth(authStr string) (string, string, error) {
 	if n > decLen {
 		return "", "", fmt.Errorf("Something went wrong decoding auth config")
 	}
-	arr := strings.SplitN(string(decoded), ":", 2)
+	arr := strings.Split(string(decoded), ":")
 	if len(arr) != 2 {
 		return "", "", fmt.Errorf("Invalid auth configuration file")
 	}
@@ -163,7 +163,7 @@ func Login(authConfig *AuthConfig, factory *utils.HTTPRequestFactory) (string, e
 
 	loginAgainstOfficialIndex := serverAddress == IndexServerAddress()
 
-	// to avoid sending the server address to the server it should be removed before being marshalled
+	// to avoid sending the server address to the server it should be removed before marshalled
 	authCopy := *authConfig
 	authCopy.ServerAddress = ""
 
@@ -192,6 +192,13 @@ func Login(authConfig *AuthConfig, factory *utils.HTTPRequestFactory) (string, e
 		} else {
 			status = "Account created. Please see the documentation of the registry " + serverAddress + " for instructions how to activate it."
 		}
+	} else if reqStatusCode == 403 {
+		if loginAgainstOfficialIndex {
+			return "", fmt.Errorf("Login: Your account hasn't been activated. " +
+				"Please check your e-mail for a confirmation link.")
+		}
+		return "", fmt.Errorf("Login: Your account hasn't been activated. " +
+			"Please see the documentation of the registry " + serverAddress + " for instructions how to activate it.")
 	} else if reqStatusCode == 400 {
 		if string(reqBody) == "\"Username or email already exists\"" {
 			req, err := factory.NewRequest("GET", serverAddress+"users/", nil)
@@ -209,39 +216,13 @@ func Login(authConfig *AuthConfig, factory *utils.HTTPRequestFactory) (string, e
 				status = "Login Succeeded"
 			} else if resp.StatusCode == 401 {
 				return "", fmt.Errorf("Wrong login/password, please try again")
-			} else if resp.StatusCode == 403 {
-				if loginAgainstOfficialIndex {
-					return "", fmt.Errorf("Login: Account is not Active. Please check your e-mail for a confirmation link.")
-				}
-				return "", fmt.Errorf("Login: Account is not Active. Please see the documentation of the registry %s for instructions how to activate it.", serverAddress)
 			} else {
-				return "", fmt.Errorf("Login: %s (Code: %d; Headers: %s)", body, resp.StatusCode, resp.Header)
+				return "", fmt.Errorf("Login: %s (Code: %d; Headers: %s)", body,
+					resp.StatusCode, resp.Header)
 			}
 		} else {
 			return "", fmt.Errorf("Registration: %s", reqBody)
 		}
-	} else if reqStatusCode == 401 {
-		// This case would happen with private registries where /v1/users is
-		// protected, so people can use `docker login` as an auth check.
-		req, err := factory.NewRequest("GET", serverAddress+"users/", nil)
-		req.SetBasicAuth(authConfig.Username, authConfig.Password)
-		resp, err := client.Do(req)
-		if err != nil {
-			return "", err
-		}
-		defer resp.Body.Close()
-		body, err := ioutil.ReadAll(resp.Body)
-		if err != nil {
-			return "", err
-		}
-		if resp.StatusCode == 200 {
-			status = "Login Succeeded"
-		} else if resp.StatusCode == 401 {
-			return "", fmt.Errorf("Wrong login/password, please try again")
-		} else {
-			return "", fmt.Errorf("Login: %s (Code: %d; Headers: %s)", body,
-				resp.StatusCode, resp.Header)
-		}
 	} else {
 		return "", fmt.Errorf("Unexpected status code [%d] : %s", reqStatusCode, reqBody)
 	}
@@ -254,11 +235,11 @@ func (config *ConfigFile) ResolveAuthConfig(registry string) AuthConfig {
 		// default to the index server
 		return config.Configs[IndexServerAddress()]
 	}
-	// if it's not the index server there are three cases:
+	// if its not the index server there are three cases:
 	//
-	// 1. a full config url -> it should be used as is
-	// 2. a full url, but with the wrong protocol
-	// 3. a hostname, with an optional port
+	// 1. this is a full config url -> it should be used as is
+	// 2. it could be a full url, but with the wrong protocol
+	// 3. it can be the hostname optionally with a port
 	//
 	// as there is only one auth entry which is fully qualified we need to start
 	// parsing and matching

buildfile.go

@@ -1,30 +1,20 @@
 package docker
 
 import (
-	"crypto/sha256"
-	"encoding/hex"
 	"encoding/json"
-	"errors"
 	"fmt"
 	"github.com/dotcloud/docker/archive"
-	"github.com/dotcloud/docker/auth"
 	"github.com/dotcloud/docker/utils"
 	"io"
 	"io/ioutil"
 	"net/url"
 	"os"
 	"path"
-	"path/filepath"
 	"reflect"
 	"regexp"
-	"sort"
 	"strings"
 )
 
-var (
-	ErrDockerfileEmpty = errors.New("Dockerfile cannot be empty")
-)
-
 type BuildFile interface {
 	Build(io.Reader) (string, error)
 	CmdFrom(string) error
@@ -35,35 +25,25 @@ type buildFile struct {
 	runtime *Runtime
 	srv     *Server
 
-	image      string
-	maintainer string
-	config     *Config
-
-	contextPath string
-	context     *utils.TarSum
-
+	image        string
+	maintainer   string
+	config       *Config
+	context      string
 	verbose      bool
 	utilizeCache bool
 	rm           bool
 
-	authConfig *auth.AuthConfig
-
 	tmpContainers map[string]struct{}
 	tmpImages     map[string]struct{}
 
-	outStream io.Writer
-	errStream io.Writer
-
-	// Deprecated, original writer used for ImagePull. To be removed.
-	outOld io.Writer
-	sf     *utils.StreamFormatter
+	out io.Writer
 }
 
 func (b *buildFile) clearTmp(containers map[string]struct{}) {
 	for c := range containers {
 		tmp := b.runtime.Get(c)
 		b.runtime.Destroy(tmp)
-		fmt.Fprintf(b.outStream, "Removing intermediate container %s\n", utils.TruncateID(c))
+		fmt.Fprintf(b.out, "Removing intermediate container %s\n", utils.TruncateID(c))
 	}
 }
 
@@ -72,7 +52,7 @@ func (b *buildFile) CmdFrom(name string) error {
 	if err != nil {
 		if b.runtime.graph.IsNotExist(err) {
 			remote, tag := utils.ParseRepositoryTag(name)
-			if err := b.srv.ImagePull(remote, tag, b.outOld, b.sf, b.authConfig, nil, true); err != nil {
+			if err := b.srv.ImagePull(remote, tag, b.out, utils.NewStreamFormatter(false), nil, nil, true); err != nil {
 				return err
 			}
 			image, err = b.runtime.repositories.LookupImage(name)
@@ -99,27 +79,6 @@ func (b *buildFile) CmdMaintainer(name string) error {
 	return b.commit("", b.config.Cmd, fmt.Sprintf("MAINTAINER %s", name))
 }
 
-// probeCache checks to see if image-caching is enabled (`b.utilizeCache`)
-// and if so attempts to look up the current `b.image` and `b.config` pair
-// in the current server `b.srv`. If an image is found, probeCache returns
-// `(true, nil)`. If no image is found, it returns `(false, nil)`. If there
-// is any error, it returns `(false, err)`.
-func (b *buildFile) probeCache() (bool, error) {
-	if b.utilizeCache {
-		if cache, err := b.srv.ImageGetCached(b.image, b.config); err != nil {
-			return false, err
-		} else if cache != nil {
-			fmt.Fprintf(b.outStream, " ---> Using cache\n")
-			utils.Debugf("[BUILDER] Use cached version")
-			b.image = cache.ID
-			return true, nil
-		} else {
-			utils.Debugf("[BUILDER] Cache miss")
-		}
-	}
-	return false, nil
-}
-
 func (b *buildFile) CmdRun(args string) error {
 	if b.image == "" {
 		return fmt.Errorf("Please provide a source image with `from` prior to run")
@@ -137,12 +96,17 @@ func (b *buildFile) CmdRun(args string) error {
 
 	utils.Debugf("Command to be executed: %v", b.config.Cmd)
 
-	hit, err := b.probeCache()
-	if err != nil {
-		return err
-	}
-	if hit {
-		return nil
+	if b.utilizeCache {
+		if cache, err := b.srv.ImageGetCached(b.image, b.config); err != nil {
+			return err
+		} else if cache != nil {
+			fmt.Fprintf(b.out, " ---> Using cache\n")
+			utils.Debugf("[BUILDER] Use cached version")
+			b.image = cache.ID
+			return nil
+		} else {
+			utils.Debugf("[BUILDER] Cache miss")
+		}
 	}
 
 	cid, err := b.run()
@@ -277,7 +241,7 @@ func (b *buildFile) CmdVolume(args string) error {
 		volume = []string{args}
 	}
 	if b.config.Volumes == nil {
-		b.config.Volumes = map[string]struct{}{}
+		b.config.Volumes = NewPathOpts()
 	}
 	for _, v := range volume {
 		b.config.Volumes[v] = struct{}{}
@@ -288,27 +252,44 @@ func (b *buildFile) CmdVolume(args string) error {
 	return nil
 }
 
-func (b *buildFile) checkPathForAddition(orig string) error {
-	origPath := path.Join(b.contextPath, orig)
-	if !strings.HasPrefix(origPath, b.contextPath) {
-		return fmt.Errorf("Forbidden path outside the build context: %s (%s)", orig, origPath)
-	}
-	_, err := os.Stat(origPath)
+func (b *buildFile) addRemote(container *Container, orig, dest string) error {
+	file, err := utils.Download(orig, ioutil.Discard)
 	if err != nil {
-		return fmt.Errorf("%s: no such file or directory", orig)
+		return err
 	}
-	return nil
+	defer file.Body.Close()
+
+	// If the destination is a directory, figure out the filename.
+	if strings.HasSuffix(dest, "/") {
+		u, err := url.Parse(orig)
+		if err != nil {
+			return err
+		}
+		path := u.Path
+		if strings.HasSuffix(path, "/") {
+			path = path[:len(path)-1]
+		}
+		parts := strings.Split(path, "/")
+		filename := parts[len(parts)-1]
+		if filename == "" {
+			return fmt.Errorf("cannot determine filename from url: %s", u)
+		}
+		dest = dest + filename
+	}
+
+	return container.Inject(file.Body, dest)
 }
 
 func (b *buildFile) addContext(container *Container, orig, dest string) error {
-	var (
-		origPath = path.Join(b.contextPath, orig)
-		destPath = path.Join(container.RootfsPath(), dest)
-	)
+	origPath := path.Join(b.context, orig)
+	destPath := path.Join(container.RootfsPath(), dest)
 	// Preserve the trailing '/'
 	if strings.HasSuffix(dest, "/") {
 		destPath = destPath + "/"
 	}
+	if !strings.HasPrefix(origPath, b.context) {
+		return fmt.Errorf("Forbidden path: %s", origPath)
+	}
 	fi, err := os.Stat(origPath)
 	if err != nil {
 		return fmt.Errorf("%s: no such file or directory", orig)
@@ -332,7 +313,7 @@ func (b *buildFile) addContext(container *Container, orig, dest string) error {
 }
 
 func (b *buildFile) CmdAdd(args string) error {
-	if b.context == nil {
+	if b.context == "" {
 		return fmt.Errorf("No context given. Impossible to use ADD")
 	}
 	tmp := strings.SplitN(args, " ", 2)
@@ -352,90 +333,8 @@ func (b *buildFile) CmdAdd(args string) error {
 
 	cmd := b.config.Cmd
 	b.config.Cmd = []string{"/bin/sh", "-c", fmt.Sprintf("#(nop) ADD %s in %s", orig, dest)}
+
 	b.config.Image = b.image
-
-	// FIXME: do we really need this?
-	var (
-		origPath = orig
-		destPath = dest
-	)
-
-	if utils.IsURL(orig) {
-		resp, err := utils.Download(orig)
-		if err != nil {
-			return err
-		}
-		tmpDirName, err := ioutil.TempDir(b.contextPath, "docker-remote")
-		if err != nil {
-			return err
-		}
-		tmpFileName := path.Join(tmpDirName, "tmp")
-		tmpFile, err := os.OpenFile(tmpFileName, os.O_RDWR|os.O_CREATE|os.O_EXCL, 0600)
-		if err != nil {
-			return err
-		}
-		defer os.RemoveAll(tmpDirName)
-		if _, err = io.Copy(tmpFile, resp.Body); err != nil {
-			return err
-		}
-		origPath = path.Join(filepath.Base(tmpDirName), filepath.Base(tmpFileName))
-		tmpFile.Close()
-
-		// If the destination is a directory, figure out the filename.
-		if strings.HasSuffix(dest, "/") {
-			u, err := url.Parse(orig)
-			if err != nil {
-				return err
-			}
-			path := u.Path
-			if strings.HasSuffix(path, "/") {
-				path = path[:len(path)-1]
-			}
-			parts := strings.Split(path, "/")
-			filename := parts[len(parts)-1]
-			if filename == "" {
-				return fmt.Errorf("cannot determine filename from url: %s", u)
-			}
-			destPath = dest + filename
-		}
-	}
-
-	if err := b.checkPathForAddition(origPath); err != nil {
-		return err
-	}
-
-	// Hash path and check the cache
-	if b.utilizeCache {
-		var (
-			hash string
-			sums = b.context.GetSums()
-		)
-		if fi, err := os.Stat(path.Join(b.contextPath, origPath)); err != nil {
-			return err
-		} else if fi.IsDir() {
-			var subfiles []string
-			for file, sum := range sums {
-				if strings.HasPrefix(file, origPath) {
-					subfiles = append(subfiles, sum)
-				}
-			}
-			sort.Strings(subfiles)
-			hasher := sha256.New()
-			hasher.Write([]byte(strings.Join(subfiles, ",")))
-			hash = "dir:" + hex.EncodeToString(hasher.Sum(nil))
-		} else {
-			hash = "file:" + sums[origPath]
-		}
-		b.config.Cmd = []string{"/bin/sh", "-c", fmt.Sprintf("#(nop) ADD %s in %s", hash, dest)}
-		hit, err := b.probeCache()
-		if err != nil {
-			return err
-		}
-		if hit {
-			return nil
-		}
-	}
-
 	// Create the container and start it
 	container, _, err := b.runtime.Create(b.config, "")
 	if err != nil {
@@ -448,8 +347,14 @@ func (b *buildFile) CmdAdd(args string) error {
 	}
 	defer container.Unmount()
 
-	if err := b.addContext(container, origPath, destPath); err != nil {
-		return err
+	if utils.IsURL(orig) {
+		if err := b.addRemote(container, orig, dest); err != nil {
+			return err
+		}
+	} else {
+		if err := b.addContext(container, orig, dest); err != nil {
+			return err
+		}
 	}
 
 	if err := b.commit(container.ID, cmd, fmt.Sprintf("ADD %s in %s", orig, dest)); err != nil {
@@ -459,34 +364,6 @@ func (b *buildFile) CmdAdd(args string) error {
 	return nil
 }
 
-type StdoutFormater struct {
-	io.Writer
-	*utils.StreamFormatter
-}
-
-func (sf *StdoutFormater) Write(buf []byte) (int, error) {
-	formattedBuf := sf.StreamFormatter.FormatStream(string(buf))
-	n, err := sf.Writer.Write(formattedBuf)
-	if n != len(formattedBuf) {
-		return n, io.ErrShortWrite
-	}
-	return len(buf), err
-}
-
-type StderrFormater struct {
-	io.Writer
-	*utils.StreamFormatter
-}
-
-func (sf *StderrFormater) Write(buf []byte) (int, error) {
-	formattedBuf := sf.StreamFormatter.FormatStream("\033[91m" + string(buf) + "\033[0m")
-	n, err := sf.Writer.Write(formattedBuf)
-	if n != len(formattedBuf) {
-		return n, io.ErrShortWrite
-	}
-	return len(buf), err
-}
-
 func (b *buildFile) run() (string, error) {
 	if b.image == "" {
 		return "", fmt.Errorf("Please provide a source image with `from` prior to run")
@@ -499,7 +376,7 @@ func (b *buildFile) run() (string, error) {
 		return "", err
 	}
 	b.tmpContainers[c.ID] = struct{}{}
-	fmt.Fprintf(b.outStream, " ---> Running in %s\n", utils.TruncateID(c.ID))
+	fmt.Fprintf(b.out, " ---> Running in %s\n", utils.TruncateID(c.ID))
 
 	// override the entry point that may have been picked up from the base image
 	c.Path = b.config.Cmd[0]
@@ -509,7 +386,7 @@ func (b *buildFile) run() (string, error) {
 
 	if b.verbose {
 		errCh = utils.Go(func() error {
-			return <-c.Attach(nil, nil, b.outStream, b.errStream)
+			return <-c.Attach(nil, nil, b.out, b.out)
 		})
 	}
 
@@ -526,11 +403,7 @@ func (b *buildFile) run() (string, error) {
 
 	// Wait for it to finish
 	if ret := c.Wait(); ret != 0 {
-		err := &utils.JSONError{
-			Message: fmt.Sprintf("The command %v returned a non-zero code: %d", b.config.Cmd, ret),
-			Code:    ret,
-		}
-		return "", err
+		return "", fmt.Errorf("The command %v returned a non-zero code: %d", b.config.Cmd, ret)
 	}
 
 	return c.ID, nil
@@ -547,12 +420,17 @@ func (b *buildFile) commit(id string, autoCmd []string, comment string) error {
 		b.config.Cmd = []string{"/bin/sh", "-c", "#(nop) " + comment}
 		defer func(cmd []string) { b.config.Cmd = cmd }(cmd)
 
-		hit, err := b.probeCache()
-		if err != nil {
-			return err
-		}
-		if hit {
-			return nil
+		if b.utilizeCache {
+			if cache, err := b.srv.ImageGetCached(b.image, b.config); err != nil {
+				return err
+			} else if cache != nil {
+				fmt.Fprintf(b.out, " ---> Using cache\n")
+				utils.Debugf("[BUILDER] Use cached version")
+				b.image = cache.ID
+				return nil
+			} else {
+				utils.Debugf("[BUILDER] Cache miss")
+			}
 		}
 
 		container, warnings, err := b.runtime.Create(b.config, "")
@@ -560,10 +438,10 @@ func (b *buildFile) commit(id string, autoCmd []string, comment string) error {
 			return err
 		}
 		for _, warning := range warnings {
-			fmt.Fprintf(b.outStream, " ---> [Warning] %s\n", warning)
+			fmt.Fprintf(b.out, " ---> [Warning] %s\n", warning)
 		}
 		b.tmpContainers[container.ID] = struct{}{}
-		fmt.Fprintf(b.outStream, " ---> Running in %s\n", utils.TruncateID(container.ID))
+		fmt.Fprintf(b.out, " ---> Running in %s\n", utils.TruncateID(container.ID))
 		id = container.ID
 		if err := container.EnsureMounted(); err != nil {
 			return err
@@ -593,17 +471,17 @@ func (b *buildFile) commit(id string, autoCmd []string, comment string) error {
 var lineContinuation = regexp.MustCompile(`\s*\\\s*\n`)
 
 func (b *buildFile) Build(context io.Reader) (string, error) {
-	tmpdirPath, err := ioutil.TempDir("", "docker-build")
+	// FIXME: @creack "name" is a terrible variable name
+	name, err := ioutil.TempDir("", "docker-build")
 	if err != nil {
 		return "", err
 	}
-	b.context = &utils.TarSum{Reader: context}
-	if err := archive.Untar(b.context, tmpdirPath, nil); err != nil {
+	if err := archive.Untar(context, name, nil); err != nil {
 		return "", err
 	}
-	defer os.RemoveAll(tmpdirPath)
-	b.contextPath = tmpdirPath
-	filename := path.Join(tmpdirPath, "Dockerfile")
+	defer os.RemoveAll(name)
+	b.context = name
+	filename := path.Join(name, "Dockerfile")
 	if _, err := os.Stat(filename); os.IsNotExist(err) {
 		return "", fmt.Errorf("Can't build a directory with no Dockerfile")
 	}
@@ -611,9 +489,6 @@ func (b *buildFile) Build(context io.Reader) (string, error) {
 	if err != nil {
 		return "", err
 	}
-	if len(fileBytes) == 0 {
-		return "", ErrDockerfileEmpty
-	}
 	dockerfile := string(fileBytes)
 	dockerfile = lineContinuation.ReplaceAllString(dockerfile, "")
 	stepN := 0
@@ -632,22 +507,22 @@ func (b *buildFile) Build(context io.Reader) (string, error) {
 
 		method, exists := reflect.TypeOf(b).MethodByName("Cmd" + strings.ToUpper(instruction[:1]) + strings.ToLower(instruction[1:]))
 		if !exists {
-			fmt.Fprintf(b.errStream, "# Skipping unknown instruction %s\n", strings.ToUpper(instruction))
+			fmt.Fprintf(b.out, "# Skipping unknown instruction %s\n", strings.ToUpper(instruction))
 			continue
 		}
 
 		stepN += 1
-		fmt.Fprintf(b.outStream, "Step %d : %s %s\n", stepN, strings.ToUpper(instruction), arguments)
+		fmt.Fprintf(b.out, "Step %d : %s %s\n", stepN, strings.ToUpper(instruction), arguments)
 
 		ret := method.Func.Call([]reflect.Value{reflect.ValueOf(b), reflect.ValueOf(arguments)})[0].Interface()
 		if ret != nil {
 			return "", ret.(error)
 		}
 
-		fmt.Fprintf(b.outStream, " ---> %s\n", utils.TruncateID(b.image))
+		fmt.Fprintf(b.out, " ---> %v\n", utils.TruncateID(b.image))
 	}
 	if b.image != "" {
-		fmt.Fprintf(b.outStream, "Successfully built %s\n", utils.TruncateID(b.image))
+		fmt.Fprintf(b.out, "Successfully built %s\n", utils.TruncateID(b.image))
 		if b.rm {
 			b.clearTmp(b.tmpContainers)
 		}
@@ -656,20 +531,16 @@ func (b *buildFile) Build(context io.Reader) (string, error) {
 	return "", fmt.Errorf("An error occurred during the build\n")
 }
 
-func NewBuildFile(srv *Server, outStream, errStream io.Writer, verbose, utilizeCache, rm bool, outOld io.Writer, sf *utils.StreamFormatter, auth *auth.AuthConfig) BuildFile {
+func NewBuildFile(srv *Server, out io.Writer, verbose, utilizeCache, rm bool) BuildFile {
 	return &buildFile{
 		runtime:       srv.runtime,
 		srv:           srv,
 		config:        &Config{},
-		outStream:     outStream,
-		errStream:     errStream,
+		out:           out,
 		tmpContainers: make(map[string]struct{}),
 		tmpImages:     make(map[string]struct{}),
 		verbose:       verbose,
 		utilizeCache:  utilizeCache,
 		rm:            rm,
-		sf:            sf,
-		authConfig:    auth,
-		outOld:        outOld,
 	}
 }

commands_unit_test.go

@@ -1,159 +0,0 @@
-package docker
-
-import (
-	"strings"
-	"testing"
-)
-
-func parse(t *testing.T, args string) (*Config, *HostConfig, error) {
-	config, hostConfig, _, err := ParseRun(strings.Split(args+" ubuntu bash", " "), nil)
-	return config, hostConfig, err
-}
-
-func mustParse(t *testing.T, args string) (*Config, *HostConfig) {
-	config, hostConfig, err := parse(t, args)
-	if err != nil {
-		t.Fatal(err)
-	}
-	return config, hostConfig
-}
-
-func TestParseRunLinks(t *testing.T) {
-	if _, hostConfig := mustParse(t, "-link a:b"); len(hostConfig.Links) == 0 || hostConfig.Links[0] != "a:b" {
-		t.Fatalf("Error parsing links. Expected []string{\"a:b\"}, received: %v", hostConfig.Links)
-	}
-	if _, hostConfig := mustParse(t, "-link a:b -link c:d"); len(hostConfig.Links) < 2 || hostConfig.Links[0] != "a:b" || hostConfig.Links[1] != "c:d" {
-		t.Fatalf("Error parsing links. Expected []string{\"a:b\", \"c:d\"}, received: %v", hostConfig.Links)
-	}
-	if _, hostConfig := mustParse(t, ""); len(hostConfig.Links) != 0 {
-		t.Fatalf("Error parsing links. No link expected, received: %v", hostConfig.Links)
-	}
-
-	if _, _, err := parse(t, "-link a"); err == nil {
-		t.Fatalf("Error parsing links. `-link a` should be an error but is not")
-	}
-	if _, _, err := parse(t, "-link"); err == nil {
-		t.Fatalf("Error parsing links. `-link` should be an error but is not")
-	}
-}
-
-func TestParseRunAttach(t *testing.T) {
-	if config, _ := mustParse(t, "-a stdin"); !config.AttachStdin || config.AttachStdout || config.AttachStderr {
-		t.Fatalf("Error parsing attach flags. Expect only Stdin enabled. Received: in: %v, out: %v, err: %v", config.AttachStdin, config.AttachStdout, config.AttachStderr)
-	}
-	if config, _ := mustParse(t, "-a stdin -a stdout"); !config.AttachStdin || !config.AttachStdout || config.AttachStderr {
-		t.Fatalf("Error parsing attach flags. Expect only Stdin and Stdout enabled. Received: in: %v, out: %v, err: %v", config.AttachStdin, config.AttachStdout, config.AttachStderr)
-	}
-	if config, _ := mustParse(t, "-a stdin -a stdout -a stderr"); !config.AttachStdin || !config.AttachStdout || !config.AttachStderr {
-		t.Fatalf("Error parsing attach flags. Expect all attach enabled. Received: in: %v, out: %v, err: %v", config.AttachStdin, config.AttachStdout, config.AttachStderr)
-	}
-	if config, _ := mustParse(t, ""); config.AttachStdin || !config.AttachStdout || !config.AttachStderr {
-		t.Fatalf("Error parsing attach flags. Expect Stdin disabled. Received: in: %v, out: %v, err: %v", config.AttachStdin, config.AttachStdout, config.AttachStderr)
-	}
-
-	if _, _, err := parse(t, "-a"); err == nil {
-		t.Fatalf("Error parsing attach flags, `-a` should be an error but is not")
-	}
-	if _, _, err := parse(t, "-a invalid"); err == nil {
-		t.Fatalf("Error parsing attach flags, `-a invalid` should be an error but is not")
-	}
-	if _, _, err := parse(t, "-a invalid -a stdout"); err == nil {
-		t.Fatalf("Error parsing attach flags, `-a stdout -a invalid` should be an error but is not")
-	}
-	if _, _, err := parse(t, "-a stdout -a stderr -d"); err == nil {
-		t.Fatalf("Error parsing attach flags, `-a stdout -a stderr -d` should be an error but is not")
-	}
-	if _, _, err := parse(t, "-a stdin -d"); err == nil {
-		t.Fatalf("Error parsing attach flags, `-a stdin -d` should be an error but is not")
-	}
-	if _, _, err := parse(t, "-a stdout -d"); err == nil {
-		t.Fatalf("Error parsing attach flags, `-a stdout -d` should be an error but is not")
-	}
-	if _, _, err := parse(t, "-a stderr -d"); err == nil {
-		t.Fatalf("Error parsing attach flags, `-a stderr -d` should be an error but is not")
-	}
-	if _, _, err := parse(t, "-d -rm"); err == nil {
-		t.Fatalf("Error parsing attach flags, `-d -rm` should be an error but is not")
-	}
-}
-
-func TestParseRunVolumes(t *testing.T) {
-	if config, hostConfig := mustParse(t, "-v /tmp"); hostConfig.Binds != nil {
-		t.Fatalf("Error parsing volume flags, `-v /tmp` should not mount-bind anything. Received %v", hostConfig.Binds)
-	} else if _, exists := config.Volumes["/tmp"]; !exists {
-		t.Fatalf("Error parsing volume flags, `-v /tmp` is missing from volumes. Received %v", config.Volumes)
-	}
-
-	if config, hostConfig := mustParse(t, "-v /tmp -v /var"); hostConfig.Binds != nil {
-		t.Fatalf("Error parsing volume flags, `-v /tmp -v /var` should not mount-bind anything. Received %v", hostConfig.Binds)
-	} else if _, exists := config.Volumes["/tmp"]; !exists {
-		t.Fatalf("Error parsing volume flags, `-v /tmp` is missing from volumes. Recevied %v", config.Volumes)
-	} else if _, exists := config.Volumes["/var"]; !exists {
-		t.Fatalf("Error parsing volume flags, `-v /var` is missing from volumes. Received %v", config.Volumes)
-	}
-
-	if config, hostConfig := mustParse(t, "-v /hostTmp:/containerTmp"); hostConfig.Binds == nil || hostConfig.Binds[0] != "/hostTmp:/containerTmp" {
-		t.Fatalf("Error parsing volume flags, `-v /hostTmp:/containerTmp` should mount-bind /hostTmp into /containeTmp. Received %v", hostConfig.Binds)
-	} else if _, exists := config.Volumes["/containerTmp"]; !exists {
-		t.Fatalf("Error parsing volume flags, `-v /tmp` is missing from volumes. Received %v", config.Volumes)
-	}
-
-	if config, hostConfig := mustParse(t, "-v /hostTmp:/containerTmp -v /hostVar:/containerVar"); hostConfig.Binds == nil || hostConfig.Binds[0] != "/hostTmp:/containerTmp" || hostConfig.Binds[1] != "/hostVar:/containerVar" {
-		t.Fatalf("Error parsing volume flags, `-v /hostTmp:/containerTmp -v /hostVar:/containerVar` should mount-bind /hostTmp into /containeTmp and /hostVar into /hostContainer. Received %v", hostConfig.Binds)
-	} else if _, exists := config.Volumes["/containerTmp"]; !exists {
-		t.Fatalf("Error parsing volume flags, `-v /containerTmp` is missing from volumes. Received %v", config.Volumes)
-	} else if _, exists := config.Volumes["/containerVar"]; !exists {
-		t.Fatalf("Error parsing volume flags, `-v /containerVar` is missing from volumes. Received %v", config.Volumes)
-	}
-
-	if config, hostConfig := mustParse(t, "-v /hostTmp:/containerTmp:ro -v /hostVar:/containerVar:rw"); hostConfig.Binds == nil || hostConfig.Binds[0] != "/hostTmp:/containerTmp:ro" || hostConfig.Binds[1] != "/hostVar:/containerVar:rw" {
-		t.Fatalf("Error parsing volume flags, `-v /hostTmp:/containerTmp:ro -v /hostVar:/containerVar:rw` should mount-bind /hostTmp into /containeTmp and /hostVar into /hostContainer. Received %v", hostConfig.Binds)
-	} else if _, exists := config.Volumes["/containerTmp"]; !exists {
-		t.Fatalf("Error parsing volume flags, `-v /containerTmp` is missing from volumes. Received %v", config.Volumes)
-	} else if _, exists := config.Volumes["/containerVar"]; !exists {
-		t.Fatalf("Error parsing volume flags, `-v /containerVar` is missing from volumes. Received %v", config.Volumes)
-	}
-
-	if config, hostConfig := mustParse(t, "-v /hostTmp:/containerTmp -v /containerVar"); hostConfig.Binds == nil || len(hostConfig.Binds) > 1 || hostConfig.Binds[0] != "/hostTmp:/containerTmp" {
-		t.Fatalf("Error parsing volume flags, `-v /hostTmp:/containerTmp -v /containerVar` should mount-bind only /hostTmp into /containeTmp. Received %v", hostConfig.Binds)
-	} else if _, exists := config.Volumes["/containerTmp"]; !exists {
-		t.Fatalf("Error parsing volume flags, `-v /containerTmp` is missing from volumes. Received %v", config.Volumes)
-	} else if _, exists := config.Volumes["/containerVar"]; !exists {
-		t.Fatalf("Error parsing volume flags, `-v /containerVar` is missing from volumes. Received %v", config.Volumes)
-	}
-
-	if config, hostConfig := mustParse(t, ""); hostConfig.Binds != nil {
-		t.Fatalf("Error parsing volume flags, without volume, nothing should be mount-binded. Received %v", hostConfig.Binds)
-	} else if len(config.Volumes) != 0 {
-		t.Fatalf("Error parsing volume flags, without volume, no volume should be present. Received %v", config.Volumes)
-	}
-
-	if _, _, err := parse(t, "-v /"); err == nil {
-		t.Fatalf("Expected error, but got none")
-	}
-
-	if _, _, err := parse(t, "-v /:/"); err == nil {
-		t.Fatalf("Error parsing volume flags, `-v /:/` should fail but didn't")
-	}
-	if _, _, err := parse(t, "-v"); err == nil {
-		t.Fatalf("Error parsing volume flags, `-v` should fail but didn't")
-	}
-	if _, _, err := parse(t, "-v /tmp:"); err == nil {
-		t.Fatalf("Error parsing volume flags, `-v /tmp:` should fail but didn't")
-	}
-	if _, _, err := parse(t, "-v /tmp:ro"); err == nil {
-		t.Fatalf("Error parsing volume flags, `-v /tmp:ro` should fail but didn't")
-	}
-	if _, _, err := parse(t, "-v /tmp::"); err == nil {
-		t.Fatalf("Error parsing volume flags, `-v /tmp::` should fail but didn't")
-	}
-	if _, _, err := parse(t, "-v :"); err == nil {
-		t.Fatalf("Error parsing volume flags, `-v :` should fail but didn't")
-	}
-	if _, _, err := parse(t, "-v ::"); err == nil {
-		t.Fatalf("Error parsing volume flags, `-v ::` should fail but didn't")
-	}
-	if _, _, err := parse(t, "-v /tmp:/tmp:/tmp:/tmp"); err == nil {
-		t.Fatalf("Error parsing volume flags, `-v /tmp:/tmp:/tmp:/tmp` should fail but didn't")
-	}
-}

config.go

@@ -14,11 +14,9 @@ type DaemonConfig struct {
 	Dns                         []string
 	EnableIptables              bool
 	BridgeIface                 string
-	BridgeIp                    string
 	DefaultIp                   net.IP
 	InterContainerCommunication bool
 	GraphDriver                 string
-	Mtu                         int
 }
 
 // ConfigFromJob creates and returns a new DaemonConfig object
@@ -29,8 +27,8 @@ func ConfigFromJob(job *engine.Job) *DaemonConfig {
 	config.Root = job.Getenv("Root")
 	config.AutoRestart = job.GetenvBool("AutoRestart")
 	config.EnableCors = job.GetenvBool("EnableCors")
-	if dns := job.GetenvList("Dns"); dns != nil {
-		config.Dns = dns
+	if dns := job.Getenv("Dns"); dns != "" {
+		config.Dns = []string{dns}
 	}
 	config.EnableIptables = job.GetenvBool("EnableIptables")
 	if br := job.Getenv("BridgeIface"); br != "" {
@@ -38,14 +36,8 @@ func ConfigFromJob(job *engine.Job) *DaemonConfig {
 	} else {
 		config.BridgeIface = DefaultNetworkBridge
 	}
-	config.BridgeIp = job.Getenv("BridgeIp")
 	config.DefaultIp = net.ParseIP(job.Getenv("DefaultIp"))
 	config.InterContainerCommunication = job.GetenvBool("InterContainerCommunication")
 	config.GraphDriver = job.Getenv("GraphDriver")
-	if mtu := job.GetenvInt("Mtu"); mtu != -1 {
-		config.Mtu = mtu
-	} else {
-		config.Mtu = DefaultNetworkMtu
-	}
 	return &config
 }

container.go

@@ -7,8 +7,7 @@ import (
 	"fmt"
 	"github.com/dotcloud/docker/archive"
 	"github.com/dotcloud/docker/graphdriver"
-	"github.com/dotcloud/docker/mount"
-	"github.com/dotcloud/docker/pkg/term"
+	"github.com/dotcloud/docker/term"
 	"github.com/dotcloud/docker/utils"
 	"github.com/kr/pty"
 	"io"
@@ -25,11 +24,6 @@ import (
 	"time"
 )
 
-var (
-	ErrNotATTY = errors.New("The PTY is not a file")
-	ErrNoTTY   = errors.New("No PTY found")
-)
-
 type Container struct {
 	sync.Mutex
 	root   string // Path to the "home" of the container, including metadata.
@@ -49,6 +43,7 @@ type Container struct {
 	network         *NetworkInterface
 	NetworkSettings *NetworkSettings
 
+	SysInitPath    string
 	ResolvConfPath string
 	HostnamePath   string
 	HostsPath      string
@@ -297,11 +292,7 @@ func (container *Container) generateEnvConfig(env []string) error {
 	if err != nil {
 		return err
 	}
-	p, err := container.EnvConfigPath()
-	if err != nil {
-		return err
-	}
-	ioutil.WriteFile(p, data, 0600)
+	ioutil.WriteFile(container.EnvConfigPath(), data, 0600)
 	return nil
 }
 
@@ -545,18 +536,162 @@ func (container *Container) Start() (err error) {
 		log.Printf("WARNING: IPv4 forwarding is disabled. Networking will not work")
 	}
 
+	// Create the requested bind mounts
+	binds := make(map[string]BindMap)
+	// Define illegal container destinations
+	illegalDsts := []string{"/", "."}
+
+	for _, bind := range container.hostConfig.Binds {
+		// FIXME: factorize bind parsing in parseBind
+		var src, dst, mode string
+		arr := strings.Split(bind, ":")
+		if len(arr) == 2 {
+			src = arr[0]
+			dst = arr[1]
+			mode = "rw"
+		} else if len(arr) == 3 {
+			src = arr[0]
+			dst = arr[1]
+			mode = arr[2]
+		} else {
+			return fmt.Errorf("Invalid bind specification: %s", bind)
+		}
+
+		// Bail if trying to mount to an illegal destination
+		for _, illegal := range illegalDsts {
+			if dst == illegal {
+				return fmt.Errorf("Illegal bind destination: %s", dst)
+			}
+		}
+
+		bindMap := BindMap{
+			SrcPath: src,
+			DstPath: dst,
+			Mode:    mode,
+		}
+		binds[path.Clean(dst)] = bindMap
+	}
+
 	if container.Volumes == nil || len(container.Volumes) == 0 {
 		container.Volumes = make(map[string]string)
 		container.VolumesRW = make(map[string]bool)
 	}
 
 	// Apply volumes from another container if requested
-	if err := container.applyExternalVolumes(); err != nil {
-		return err
+	if container.Config.VolumesFrom != "" {
+		containerSpecs := strings.Split(container.Config.VolumesFrom, ",")
+		for _, containerSpec := range containerSpecs {
+			mountRW := true
+			specParts := strings.SplitN(containerSpec, ":", 2)
+			switch len(specParts) {
+			case 0:
+				return fmt.Errorf("Malformed volumes-from specification: %s", container.Config.VolumesFrom)
+			case 2:
+				switch specParts[1] {
+				case "ro":
+					mountRW = false
+				case "rw": // mountRW is already true
+				default:
+					return fmt.Errorf("Malformed volumes-from speficication: %s", containerSpec)
+				}
+			}
+			c := container.runtime.Get(specParts[0])
+			if c == nil {
+				return fmt.Errorf("Container %s not found. Impossible to mount its volumes", container.ID)
+			}
+			for volPath, id := range c.Volumes {
+				if _, exists := container.Volumes[volPath]; exists {
+					continue
+				}
+				if err := os.MkdirAll(path.Join(container.RootfsPath(), volPath), 0755); err != nil {
+					return err
+				}
+				container.Volumes[volPath] = id
+				if isRW, exists := c.VolumesRW[volPath]; exists {
+					container.VolumesRW[volPath] = isRW && mountRW
+				}
+			}
+
+		}
 	}
 
-	if err := container.createVolumes(); err != nil {
-		return err
+	volumesDriver := container.runtime.volumes.driver
+	// Create the requested volumes if they don't exist
+	for volPath := range container.Config.Volumes {
+		volPath = path.Clean(volPath)
+		// Skip existing volumes
+		if _, exists := container.Volumes[volPath]; exists {
+			continue
+		}
+		var srcPath string
+		var isBindMount bool
+		srcRW := false
+		// If an external bind is defined for this volume, use that as a source
+		if bindMap, exists := binds[volPath]; exists {
+			isBindMount = true
+			srcPath = bindMap.SrcPath
+			if strings.ToLower(bindMap.Mode) == "rw" {
+				srcRW = true
+			}
+			// Otherwise create an directory in $ROOT/volumes/ and use that
+		} else {
+
+			// Do not pass a container as the parameter for the volume creation.
+			// The graph driver using the container's information ( Image ) to
+			// create the parent.
+			c, err := container.runtime.volumes.Create(nil, nil, "", "", nil)
+			if err != nil {
+				return err
+			}
+			srcPath, err = volumesDriver.Get(c.ID)
+			if err != nil {
+				return fmt.Errorf("Driver %s failed to get volume rootfs %s: %s", volumesDriver, c.ID, err)
+			}
+			srcRW = true // RW by default
+		}
+		container.Volumes[volPath] = srcPath
+		container.VolumesRW[volPath] = srcRW
+		// Create the mountpoint
+		rootVolPath := path.Join(container.RootfsPath(), volPath)
+		if err := os.MkdirAll(rootVolPath, 0755); err != nil {
+			return err
+		}
+
+		// Do not copy or change permissions if we are mounting from the host
+		if srcRW && !isBindMount {
+			volList, err := ioutil.ReadDir(rootVolPath)
+			if err != nil {
+				return err
+			}
+			if len(volList) > 0 {
+				srcList, err := ioutil.ReadDir(srcPath)
+				if err != nil {
+					return err
+				}
+				if len(srcList) == 0 {
+					// If the source volume is empty copy files from the root into the volume
+					if err := archive.CopyWithTar(rootVolPath, srcPath); err != nil {
+						return err
+					}
+
+					var stat syscall.Stat_t
+					if err := syscall.Stat(rootVolPath, &stat); err != nil {
+						return err
+					}
+					var srcStat syscall.Stat_t
+					if err := syscall.Stat(srcPath, &srcStat); err != nil {
+						return err
+					}
+					// Change the source volume's ownership if it differs from the root
+					// files that where just copied
+					if stat.Uid != srcStat.Uid || stat.Gid != srcStat.Gid {
+						if err := os.Chown(srcPath, int(stat.Uid), int(stat.Gid)); err != nil {
+							return err
+						}
+					}
+				}
+			}
+		}
 	}
 
 	if err := container.generateLXCConfig(); err != nil {
@@ -578,12 +713,7 @@ func (container *Container) Start() (err error) {
 
 	// Networking
 	if !container.Config.NetworkDisabled {
-		network := container.NetworkSettings
-		params = append(params,
-			"-g", network.Gateway,
-			"-i", fmt.Sprintf("%s/%d", network.IPAddress, network.IPPrefixLen),
-			"-mtu", strconv.Itoa(container.runtime.config.Mtu),
-		)
+		params = append(params, "-g", container.network.Gateway.String())
 	}
 
 	// User
@@ -595,6 +725,7 @@ func (container *Container) Start() (err error) {
 	env := []string{
 		"HOME=/",
 		"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
+		"container=lxc",
 		"HOSTNAME=" + container.Config.Hostname,
 	}
 
@@ -602,10 +733,6 @@ func (container *Container) Start() (err error) {
 		env = append(env, "TERM=xterm")
 	}
 
-	if container.hostConfig.Privileged {
-		params = append(params, "-privileged")
-	}
-
 	// Init any links between the parent and children
 	runtime := container.runtime
 
@@ -686,45 +813,6 @@ func (container *Container) Start() (err error) {
 		}
 	}
 
-	root := container.RootfsPath()
-	envPath, err := container.EnvConfigPath()
-	if err != nil {
-		return err
-	}
-
-	// Mount docker specific files into the containers root fs
-	if err := mount.Mount(runtime.sysInitPath, path.Join(root, "/.dockerinit"), "none", "bind,ro"); err != nil {
-		return err
-	}
-	if err := mount.Mount(envPath, path.Join(root, "/.dockerenv"), "none", "bind,ro"); err != nil {
-		return err
-	}
-	if err := mount.Mount(container.ResolvConfPath, path.Join(root, "/etc/resolv.conf"), "none", "bind,ro"); err != nil {
-		return err
-	}
-
-	if container.HostnamePath != "" && container.HostsPath != "" {
-		if err := mount.Mount(container.HostnamePath, path.Join(root, "/etc/hostname"), "none", "bind,ro"); err != nil {
-			return err
-		}
-		if err := mount.Mount(container.HostsPath, path.Join(root, "/etc/hosts"), "none", "bind,ro"); err != nil {
-			return err
-		}
-	}
-
-	// Mount user specified volumes
-
-	for r, v := range container.Volumes {
-		mountAs := "ro"
-		if container.VolumesRW[v] {
-			mountAs = "rw"
-		}
-
-		if err := mount.Mount(v, path.Join(root, r), "none", fmt.Sprintf("bind,%s", mountAs)); err != nil {
-			return err
-		}
-	}
-
 	container.cmd = exec.Command(params[0], params[1:]...)
 
 	// Setup logging of stdout and stderr to disk
@@ -789,198 +877,6 @@ func (container *Container) Start() (err error) {
 	return ErrContainerStart
 }
 
-func (container *Container) getBindMap() (map[string]BindMap, error) {
-	// Create the requested bind mounts
-	binds := make(map[string]BindMap)
-	// Define illegal container destinations
-	illegalDsts := []string{"/", "."}
-
-	for _, bind := range container.hostConfig.Binds {
-		// FIXME: factorize bind parsing in parseBind
-		var src, dst, mode string
-		arr := strings.Split(bind, ":")
-		if len(arr) == 2 {
-			src = arr[0]
-			dst = arr[1]
-			mode = "rw"
-		} else if len(arr) == 3 {
-			src = arr[0]
-			dst = arr[1]
-			mode = arr[2]
-		} else {
-			return nil, fmt.Errorf("Invalid bind specification: %s", bind)
-		}
-
-		// Bail if trying to mount to an illegal destination
-		for _, illegal := range illegalDsts {
-			if dst == illegal {
-				return nil, fmt.Errorf("Illegal bind destination: %s", dst)
-			}
-		}
-
-		bindMap := BindMap{
-			SrcPath: src,
-			DstPath: dst,
-			Mode:    mode,
-		}
-		binds[path.Clean(dst)] = bindMap
-	}
-	return binds, nil
-}
-
-func (container *Container) createVolumes() error {
-	binds, err := container.getBindMap()
-	if err != nil {
-		return err
-	}
-	volumesDriver := container.runtime.volumes.driver
-	// Create the requested volumes if they don't exist
-	for volPath := range container.Config.Volumes {
-		volPath = path.Clean(volPath)
-		volIsDir := true
-		// Skip existing volumes
-		if _, exists := container.Volumes[volPath]; exists {
-			continue
-		}
-		var srcPath string
-		var isBindMount bool
-		srcRW := false
-		// If an external bind is defined for this volume, use that as a source
-		if bindMap, exists := binds[volPath]; exists {
-			isBindMount = true
-			srcPath = bindMap.SrcPath
-			if strings.ToLower(bindMap.Mode) == "rw" {
-				srcRW = true
-			}
-			if stat, err := os.Lstat(bindMap.SrcPath); err != nil {
-				return err
-			} else {
-				volIsDir = stat.IsDir()
-			}
-			// Otherwise create an directory in $ROOT/volumes/ and use that
-		} else {
-
-			// Do not pass a container as the parameter for the volume creation.
-			// The graph driver using the container's information ( Image ) to
-			// create the parent.
-			c, err := container.runtime.volumes.Create(nil, nil, "", "", nil)
-			if err != nil {
-				return err
-			}
-			srcPath, err = volumesDriver.Get(c.ID)
-			if err != nil {
-				return fmt.Errorf("Driver %s failed to get volume rootfs %s: %s", volumesDriver, c.ID, err)
-			}
-			srcRW = true // RW by default
-		}
-		container.Volumes[volPath] = srcPath
-		container.VolumesRW[volPath] = srcRW
-
-		// Create the mountpoint
-		volPath = path.Join(container.RootfsPath(), volPath)
-		rootVolPath, err := utils.FollowSymlinkInScope(volPath, container.RootfsPath())
-		if err != nil {
-			return err
-		}
-
-		if _, err := os.Stat(rootVolPath); err != nil {
-			if os.IsNotExist(err) {
-				if volIsDir {
-					if err := os.MkdirAll(rootVolPath, 0755); err != nil {
-						return err
-					}
-				} else {
-					if err := os.MkdirAll(path.Dir(rootVolPath), 0755); err != nil {
-						return err
-					}
-					if f, err := os.OpenFile(rootVolPath, os.O_CREATE, 0755); err != nil {
-						return err
-					} else {
-						f.Close()
-					}
-				}
-			}
-		}
-
-		// Do not copy or change permissions if we are mounting from the host
-		if srcRW && !isBindMount {
-			volList, err := ioutil.ReadDir(rootVolPath)
-			if err != nil {
-				return err
-			}
-			if len(volList) > 0 {
-				srcList, err := ioutil.ReadDir(srcPath)
-				if err != nil {
-					return err
-				}
-				if len(srcList) == 0 {
-					// If the source volume is empty copy files from the root into the volume
-					if err := archive.CopyWithTar(rootVolPath, srcPath); err != nil {
-						return err
-					}
-
-					var stat syscall.Stat_t
-					if err := syscall.Stat(rootVolPath, &stat); err != nil {
-						return err
-					}
-					var srcStat syscall.Stat_t
-					if err := syscall.Stat(srcPath, &srcStat); err != nil {
-						return err
-					}
-					// Change the source volume's ownership if it differs from the root
-					// files that where just copied
-					if stat.Uid != srcStat.Uid || stat.Gid != srcStat.Gid {
-						if err := os.Chown(srcPath, int(stat.Uid), int(stat.Gid)); err != nil {
-							return err
-						}
-					}
-				}
-			}
-		}
-	}
-	return nil
-}
-
-func (container *Container) applyExternalVolumes() error {
-	if container.Config.VolumesFrom != "" {
-		containerSpecs := strings.Split(container.Config.VolumesFrom, ",")
-		for _, containerSpec := range containerSpecs {
-			mountRW := true
-			specParts := strings.SplitN(containerSpec, ":", 2)
-			switch len(specParts) {
-			case 0:
-				return fmt.Errorf("Malformed volumes-from specification: %s", container.Config.VolumesFrom)
-			case 2:
-				switch specParts[1] {
-				case "ro":
-					mountRW = false
-				case "rw": // mountRW is already true
-				default:
-					return fmt.Errorf("Malformed volumes-from speficication: %s", containerSpec)
-				}
-			}
-			c := container.runtime.Get(specParts[0])
-			if c == nil {
-				return fmt.Errorf("Container %s not found. Impossible to mount its volumes", container.ID)
-			}
-			for volPath, id := range c.Volumes {
-				if _, exists := container.Volumes[volPath]; exists {
-					continue
-				}
-				if err := os.MkdirAll(path.Join(container.RootfsPath(), volPath), 0755); err != nil {
-					return err
-				}
-				container.Volumes[volPath] = id
-				if isRW, exists := c.VolumesRW[volPath]; exists {
-					container.VolumesRW[volPath] = isRW && mountRW
-				}
-			}
-
-		}
-	}
-	return nil
-}
-
 func (container *Container) Run() error {
 	if err := container.Start(); err != nil {
 		return err
@@ -1402,32 +1298,6 @@ func (container *Container) GetImage() (*Image, error) {
 }
 
 func (container *Container) Unmount() error {
-	var (
-		err    error
-		root   = container.RootfsPath()
-		mounts = []string{
-			path.Join(root, "/.dockerinit"),
-			path.Join(root, "/.dockerenv"),
-			path.Join(root, "/etc/resolv.conf"),
-		}
-	)
-
-	if container.HostnamePath != "" && container.HostsPath != "" {
-		mounts = append(mounts, path.Join(root, "/etc/hostname"), path.Join(root, "/etc/hosts"))
-	}
-
-	for r := range container.Volumes {
-		mounts = append(mounts, path.Join(root, r))
-	}
-
-	for _, m := range mounts {
-		if lastError := mount.Unmount(m); lastError != nil {
-			err = lastError
-		}
-	}
-	if err != nil {
-		return err
-	}
 	return container.runtime.Unmount(container)
 }
 
@@ -1447,20 +1317,8 @@ func (container *Container) jsonPath() string {
 	return path.Join(container.root, "config.json")
 }
 
-func (container *Container) EnvConfigPath() (string, error) {
-	p := path.Join(container.root, "config.env")
-	if _, err := os.Stat(p); err != nil {
-		if os.IsNotExist(err) {
-			f, err := os.Create(p)
-			if err != nil {
-				return "", err
-			}
-			f.Close()
-		} else {
-			return "", err
-		}
-	}
-	return p, nil
+func (container *Container) EnvConfigPath() string {
+	return path.Join(container.root, "config.env")
 }
 
 func (container *Container) lxcConfigPath() string {
@@ -1547,13 +1405,3 @@ func (container *Container) Exposes(p Port) bool {
 	_, exists := container.Config.ExposedPorts[p]
 	return exists
 }
-
-func (container *Container) GetPtyMaster() (*os.File, error) {
-	if container.ptyMaster == nil {
-		return nil, ErrNoTTY
-	}
-	if pty, ok := container.ptyMaster.(*os.File); ok {
-		return pty, nil
-	}
-	return nil, ErrNotATTY
-}

contrib/Dockerfile.tmLanguage/Dockerfile.tmLanguage

@@ -4,10 +4,6 @@
 <dict>
 	<key>name</key>
 	<string>Dockerfile</string>
-	<key>fileTypes</key>
-	<array>
-		<string>Dockerfile</string>
-	</array>
 	<key>patterns</key>
 	<array>
 		<dict>

contrib/completion/bash/docker

@@ -4,7 +4,7 @@
 #
 # This script provides supports completion of:
 #  - commands and their options
-#  - container ids and names
+#  - container ids
 #  - image repos and tags
 #  - filepaths
 #
@@ -25,24 +25,21 @@ __docker_containers_all()
 {
 	local containers
 	containers="$( docker ps -a -q )"
-	names="$( docker inspect -format '{{.Name}}' $containers | sed 's,^/,,' )"
-	COMPREPLY=( $( compgen -W "$names $containers" -- "$cur" ) )
+	COMPREPLY=( $( compgen -W "$containers" -- "$cur" ) )
 }
 
 __docker_containers_running()
 {
 	local containers
 	containers="$( docker ps -q )"
-	names="$( docker inspect -format '{{.Name}}' $containers | sed 's,^/,,' )"
-	COMPREPLY=( $( compgen -W "$names $containers" -- "$cur" ) )
+	COMPREPLY=( $( compgen -W "$containers" -- "$cur" ) )
 }
 
 __docker_containers_stopped()
 {
 	local containers
 	containers="$( comm -13 <(docker ps -q | sort -u) <(docker ps -a -q | sort -u) )"
-	names="$( docker inspect -format '{{.Name}}' $containers | sed 's,^/,,' )"
-	COMPREPLY=( $( compgen -W "$names $containers" -- "$cur" ) )
+	COMPREPLY=( $( compgen -W "$containers" -- "$cur" ) )
 }
 
 __docker_image_repos()
@@ -73,9 +70,8 @@ __docker_containers_and_images()
 {
 	local containers images
 	containers="$( docker ps -a -q )"
-	names="$( docker inspect -format '{{.Name}}' $containers | sed 's,^/,,' )"
 	images="$( docker images | awk 'NR>1{print $1":"$2}' )"
-	COMPREPLY=( $( compgen -W "$images $names $containers" -- "$cur" ) )
+	COMPREPLY=( $( compgen -W "$images $containers" -- "$cur" ) )
 	__ltrim_colon_completions "$cur"
 }
 

contrib/init/systemd/docker.service

@@ -1,9 +1,11 @@
 [Unit]
 Description=Docker Application Container Engine 
 Documentation=http://docs.docker.io
-After=network.target
+Requires=network.target
+After=multi-user.target
 
 [Service]
+Type=simple
 ExecStartPre=/bin/mount --make-rprivate /
 ExecStart=/usr/bin/docker -d
 

contrib/mkimage-centos.sh

@@ -0,0 +1,15 @@
+#!/bin/bash
+# Create a CentOS base image for Docker
+# From unclejack https://github.com/dotcloud/docker/issues/290
+set -e
+
+MIRROR_URL="http://centos.netnitco.net/6.4/os/x86_64/"
+MIRROR_URL_UPDATES="http://centos.netnitco.net/6.4/updates/x86_64/"
+
+yum install -y febootstrap xz
+
+febootstrap -i bash -i coreutils -i tar -i bzip2 -i gzip -i vim-minimal -i wget -i patch -i diffutils -i iproute -i yum centos centos64  $MIRROR_URL -u $MIRROR_URL_UPDATES
+touch centos64/etc/resolv.conf
+touch centos64/sbin/init
+
+tar --numeric-owner -Jcpf centos-64.tar.xz -C centos64 .

contrib/mkimage-debootstrap.sh

@@ -142,22 +142,14 @@ if [ -z "$strictDebootstrap" ]; then
 	#  this forces dpkg not to call sync() after package extraction and speeds up install
 	#    the benefit is huge on spinning disks, and the penalty is nonexistent on SSD or decent server virtualization
 	echo 'force-unsafe-io' | sudo tee etc/dpkg/dpkg.cfg.d/02apt-speedup > /dev/null
-	#  we want to effectively run "apt-get clean" after every install to keep images small (see output of "apt-get clean -s" for context)
-	{
-		aptGetClean='"rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true";'
-		echo "DPkg::Post-Invoke { ${aptGetClean} };"
-		echo "APT::Update::Post-Invoke { ${aptGetClean} };"
-		echo 'Dir::Cache::pkgcache ""; Dir::Cache::srcpkgcache "";'
-	} | sudo tee etc/apt/apt.conf.d/no-cache > /dev/null
-	#  and remove the translations, too
-	echo 'Acquire::Languages "none";' | sudo tee etc/apt/apt.conf.d/no-languages > /dev/null
+	#  we want to effectively run "apt-get clean" after every install to keep images small
+	echo 'DPkg::Post-Invoke {"/bin/rm -f /var/cache/apt/archives/*.deb || true";};' | sudo tee etc/apt/apt.conf.d/no-cache > /dev/null
 	
 	# helpful undo lines for each the above tweaks (for lack of a better home to keep track of them):
 	#  rm /usr/sbin/policy-rc.d
 	#  rm /sbin/initctl; dpkg-divert --rename --remove /sbin/initctl
 	#  rm /etc/dpkg/dpkg.cfg.d/02apt-speedup
 	#  rm /etc/apt/apt.conf.d/no-cache
-	#  rm /etc/apt/apt.conf.d/no-languages
 	
 	if [ -z "$skipDetection" ]; then
 		# see also rudimentary platform detection in hack/install.sh

contrib/mkimage-rinse.sh

@@ -1,112 +0,0 @@
-#!/bin/bash
-set -e
-
-repo="$1"
-distro="$2"
-mirror="$3"
-
-if [ ! "$repo" ] || [ ! "$distro" ]; then
-	self="$(basename $0)"
-	echo >&2 "usage: $self repo distro [mirror]"
-	echo >&2
-	echo >&2 "   ie: $self username/centos centos-5"
-	echo >&2 "       $self username/centos centos-6"
-	echo >&2
-	echo >&2 "   ie: $self username/slc slc-5"
-	echo >&2 "       $self username/slc slc-6"
-	echo >&2
-	echo >&2 "   ie: $self username/centos centos-5 http://vault.centos.org/5.8/os/x86_64/CentOS/"
-	echo >&2 "       $self username/centos centos-6 http://vault.centos.org/6.3/os/x86_64/Packages/"
-	echo >&2
-	echo >&2 'See /etc/rinse for supported values of "distro" and for examples of'
-	echo >&2 '  expected values of "mirror".'
-	echo >&2
-	echo >&2 'This script is tested to work with the original upstream version of rinse,'
-	echo >&2 '  found at http://www.steve.org.uk/Software/rinse/ and also in Debian at'
-	echo >&2 '  http://packages.debian.org/wheezy/rinse -- as always, YMMV.'
-	echo >&2
-	exit 1
-fi
-
-target="/tmp/docker-rootfs-rinse-$distro-$$-$RANDOM"
-
-cd "$(dirname "$(readlink -f "$BASH_SOURCE")")"
-returnTo="$(pwd -P)"
-
-rinseArgs=( --arch amd64 --distribution "$distro" --directory "$target" )
-if [ "$mirror" ]; then
-	rinseArgs+=( --mirror "$mirror" )
-fi
-
-set -x
-
-mkdir -p "$target"
-
-sudo rinse "${rinseArgs[@]}"
-
-cd "$target"
-
-# rinse fails a little at setting up /dev, so we'll just wipe it out and create our own
-sudo rm -rf dev
-sudo mkdir -m 755 dev
-(
-	cd dev
-	sudo ln -sf /proc/self/fd ./
-	sudo mkdir -m 755 pts
-	sudo mkdir -m 1777 shm
-	sudo mknod -m 600 console c 5 1
-	sudo mknod -m 600 initctl p
-	sudo mknod -m 666 full c 1 7
-	sudo mknod -m 666 null c 1 3
-	sudo mknod -m 666 ptmx c 5 2
-	sudo mknod -m 666 random c 1 8
-	sudo mknod -m 666 tty c 5 0
-	sudo mknod -m 666 tty0 c 4 0
-	sudo mknod -m 666 urandom c 1 9
-	sudo mknod -m 666 zero c 1 5
-)
-
-# effectively: febootstrap-minimize --keep-zoneinfo --keep-rpmdb --keep-services "$target"
-#  locales
-sudo rm -rf usr/{{lib,share}/locale,{lib,lib64}/gconv,bin/localedef,sbin/build-locale-archive}
-#  docs
-sudo rm -rf usr/share/{man,doc,info,gnome/help}
-#  cracklib
-sudo rm -rf usr/share/cracklib
-#  i18n
-sudo rm -rf usr/share/i18n
-#  yum cache
-sudo rm -rf var/cache/yum
-sudo mkdir -p --mode=0755 var/cache/yum
-#  sln
-sudo rm -rf sbin/sln
-#  ldconfig
-#sudo rm -rf sbin/ldconfig
-sudo rm -rf etc/ld.so.cache var/cache/ldconfig
-sudo mkdir -p --mode=0755 var/cache/ldconfig
-
-# allow networking init scripts inside the container to work without extra steps
-echo 'NETWORKING=yes' | sudo tee etc/sysconfig/network > /dev/null
-
-# to restore locales later:
-#  yum reinstall glibc-common
-
-version=
-if [ -r etc/redhat-release ]; then
-	version="$(sed -E 's/^[^0-9.]*([0-9.]+).*$/\1/' etc/redhat-release)"
-elif [ -r etc/SuSE-release ]; then
-	version="$(awk '/^VERSION/ { print $3 }' etc/SuSE-release)"
-fi
-
-if [ -z "$version" ]; then
-	echo >&2 "warning: cannot autodetect OS version, using $distro as tag"
-	sleep 20
-	version="$distro"
-fi
-
-sudo tar --numeric-owner -c . | docker import - $repo:$version
-
-docker run -i -t $repo:$version echo success
-
-cd "$returnTo"
-sudo rm -rf "$target"

contrib/mkseccomp.pl

@@ -1,77 +0,0 @@
-#!/usr/bin/perl
-#
-# A simple helper script to help people build seccomp profiles for
-# Docker/LXC.  The goal is mostly to reduce the attack surface to the
-# kernel, by restricting access to rarely used, recently added or not used
-# syscalls.
-#
-# This script processes one or more files which contain the list of system
-# calls to be allowed.  See mkseccomp.sample for more information how you
-# can configure the list of syscalls.  When run, this script produces output
-# which, when stored in a file, can be passed to docker as follows:
-#
-# docker run -lxc-conf="lxc.seccomp=$file" <rest of arguments>
-#
-# The included sample file shows how to cut about a quarter of all syscalls,
-# which affecting most applications.
-#
-# For specific situations it is possible to reduce the list further. By
-# reducing the list to just those syscalls required by a certain application
-# you can make it difficult for unknown/unexpected code to run.
-#
-# Run this script as follows:
-#
-# ./mkseccomp.pl < mkseccomp.sample >syscalls.list
-# or
-# ./mkseccomp.pl mkseccomp.sample >syscalls.list
-#
-# Multiple files can be specified, in which case the lists of syscalls are
-# combined.
-#
-# By Martijn van Oosterhout <kleptog@svana.org> Nov 2013
-
-# How it works:
-#
-# This program basically spawns two processes to form a chain like:
-#
-# <process data section to prefix __NR_> | cpp | <add header and filter unknown syscalls>
-
-use strict;
-use warnings;
-
-if( -t ) {
-    print STDERR "Helper script to make seccomp filters for Docker/LXC.\n";
-    print STDERR "Usage: mkseccomp.pl [files...]\n";
-    exit 1;
-}
-
-my $pid = open(my $in, "-|") // die "Couldn't fork1 ($!)\n";
-
-if($pid == 0) {  # Child
-    $pid = open(my $out, "|-") // die "Couldn't fork2 ($!)\n";
-
-    if($pid == 0) { # Child, which execs cpp
-        exec "cpp" or die "Couldn't exec cpp ($!)\n";
-        exit 1;
-    }
-
-    # Process the DATA section and output to cpp
-    print $out "#include <sys/syscall.h>\n";
-    while(<>) {
-        if(/^\w/) {
-            print $out "__NR_$_";
-        }
-    }
-    close $out;
-    exit 0;
-
-}
-
-# Print header and then process output from cpp.
-print "1\n";
-print "whitelist\n";
-
-while(<$in>) {
-    print if( /^[0-9]/ );
-}
-

contrib/mkseccomp.sample

@@ -1,444 +0,0 @@
-/* This sample file is an example for mkseccomp.pl to produce a seccomp file
- * which restricts syscalls that are only useful for an admin but allows the
- * vast majority of normal userspace programs to run normally.
- *
- * The format of this file is one line per syscall.  This is then processed
- * and passed to 'cpp' to convert the names to numbers using whatever is
- * correct for your platform.  As such C-style comments are permitted.  Note
- * this also means that C preprocessor macros are also allowed.  So it is
- * possible to create groups surrounded by #ifdef/#endif and control their
- * inclusion via #define (not #include).
- *
- * Syscalls that don't exist on your architecture are silently filtered out.
- * Syscalls marked with (*) are required for a container to spawn a bash
- * shell successfully (not necessarily full featured).  Listing the same
- * syscall multiple times is no problem.
- *
- * If you want to make a list specifically for one application the easiest
- * way is to run the application under strace, like so:
- *
- * $ strace -f -q -c -o strace.out application args...
- *
- * Once you have a reasonable sample of the execution of the program, exit
- * it.  The file strace.out will have a summary of the syscalls used.  Copy
- * that list into this file, comment out everything else except the starred
- * syscalls (which you need for the container to start) and you're done.
- *
- * To get the list of syscalls from the strace output this works well for
- * me
- *
- * $ cut -c52 < strace.out
- *
- * This sample list was compiled as a combination of all the syscalls
- * available on i386 and amd64 on Ubuntu Precise, as such it may not contain
- * everything and not everything may be relevent for your system.  This
- * shouldn't be a problem.
- */
-
-// Filesystem/File descriptor related
-access                 // (*)
-chdir                  // (*)
-chmod
-chown
-chown32
-close                  // (*)
-creat
-dup                    // (*)
-dup2                   // (*)
-dup3
-epoll_create
-epoll_create1
-epoll_ctl
-epoll_ctl_old
-epoll_pwait
-epoll_wait
-epoll_wait_old
-eventfd
-eventfd2
-faccessat              // (*)
-fadvise64
-fadvise64_64
-fallocate
-fanotify_init
-fanotify_mark
-ioctl                  // (*)
-fchdir
-fchmod
-fchmodat
-fchown
-fchown32
-fchownat
-fcntl                  // (*)
-fcntl64
-fdatasync
-fgetxattr
-flistxattr
-flock
-fremovexattr
-fsetxattr
-fstat                  // (*)
-fstat64
-fstatat64
-fstatfs
-fstatfs64
-fsync
-ftruncate
-ftruncate64
-getcwd                 // (*)
-getdents               // (*)
-getdents64
-getxattr
-inotify_add_watch
-inotify_init
-inotify_init1
-inotify_rm_watch
-io_cancel
-io_destroy
-io_getevents
-io_setup
-io_submit
-lchown
-lchown32
-lgetxattr
-link
-linkat
-listxattr
-llistxattr
-llseek
-_llseek
-lremovexattr
-lseek                  // (*)
-lsetxattr
-lstat
-lstat64
-mkdir
-mkdirat
-mknod
-mknodat
-newfstatat
-_newselect
-oldfstat
-oldlstat
-oldolduname
-oldstat
-olduname
-oldwait4
-open                   // (*)
-openat                 // (*)
-pipe                   // (*)
-pipe2
-poll
-ppoll
-pread64
-preadv
-futimesat
-pselect6
-pwrite64
-pwritev
-read                   // (*)
-readahead
-readdir
-readlink
-readlinkat
-readv
-removexattr
-rename
-renameat
-rmdir
-select
-sendfile
-sendfile64
-setxattr
-splice
-stat                   // (*)
-stat64
-statfs                 // (*)
-statfs64
-symlink
-symlinkat
-sync
-sync_file_range
-sync_file_range2
-syncfs
-tee
-truncate
-truncate64
-umask
-unlink
-unlinkat
-ustat
-utime
-utimensat
-utimes
-write                  // (*)
-writev
-
-// Network related
-accept
-accept4
-bind                   // (*)
-connect                // (*)
-getpeername
-getsockname            // (*)
-getsockopt
-listen
-recv
-recvfrom               // (*)
-recvmmsg
-recvmsg
-send
-sendmmsg
-sendmsg
-sendto                 // (*)
-setsockopt
-shutdown
-socket                 // (*)
-socketcall
-socketpair
-
-// Signal related
-pause
-rt_sigaction           // (*)
-rt_sigpending
-rt_sigprocmask         // (*)
-rt_sigqueueinfo
-rt_sigreturn           // (*)
-rt_sigsuspend
-rt_sigtimedwait
-rt_tgsigqueueinfo
-sigaction
-sigaltstack            // (*)
-signal
-signalfd
-signalfd4
-sigpending
-sigprocmask
-sigreturn
-sigsuspend
-
-// Other needed POSIX
-alarm
-brk                    // (*)
-clock_adjtime
-clock_getres
-clock_gettime
-clock_nanosleep
-//clock_settime
-gettimeofday
-nanosleep
-nice
-sysinfo
-syslog
-time
-timer_create
-timer_delete
-timerfd_create
-timerfd_gettime
-timerfd_settime
-timer_getoverrun
-timer_gettime
-timer_settime
-times
-uname                  // (*)
-
-// Memory control
-madvise
-mbind
-mincore
-mlock
-mlockall
-mmap                   // (*)
-mmap2
-mprotect               // (*)
-mremap
-msync
-munlock
-munlockall
-munmap                 // (*)
-remap_file_pages
-set_mempolicy
-vmsplice
-
-// Process control
-capget
-//capset
-clone                  // (*)
-execve                 // (*)
-exit                   // (*)
-exit_group             // (*)
-fork
-getcpu
-getpgid
-getpgrp                // (*)
-getpid                 // (*)
-getppid                // (*)
-getpriority
-getresgid
-getresgid32
-getresuid
-getresuid32
-getrlimit              // (*)
-getrusage
-getsid
-getuid                 // (*)
-getuid32
-getegid                // (*)
-getegid32
-geteuid                // (*)
-geteuid32
-getgid                 // (*)
-getgid32
-getgroups
-getgroups32
-getitimer
-get_mempolicy
-kill
-//personality
-prctl
-prlimit64
-sched_getaffinity
-sched_getparam
-sched_get_priority_max
-sched_get_priority_min
-sched_getscheduler
-sched_rr_get_interval
-//sched_setaffinity
-//sched_setparam
-//sched_setscheduler
-sched_yield
-setfsgid
-setfsgid32
-setfsuid
-setfsuid32
-setgid
-setgid32
-setgroups
-setgroups32
-setitimer
-setpgid                // (*)
-setpriority
-setregid
-setregid32
-setresgid
-setresgid32
-setresuid
-setresuid32
-setreuid
-setreuid32
-setrlimit
-setsid
-setuid
-setuid32
-ugetrlimit
-vfork
-wait4                  // (*)
-waitid
-waitpid
-
-// IPC
-ipc
-mq_getsetattr
-mq_notify
-mq_open
-mq_timedreceive
-mq_timedsend
-mq_unlink
-msgctl
-msgget
-msgrcv
-msgsnd
-semctl
-semget
-semop
-semtimedop
-shmat
-shmctl
-shmdt
-shmget
-
-// Linux specific, mostly needed for thread-related stuff
-arch_prctl             // (*)
-get_robust_list
-get_thread_area
-gettid
-futex                  // (*)
-restart_syscall        // (*)
-set_robust_list        // (*)
-set_thread_area
-set_tid_address        // (*)
-tgkill
-tkill
-
-// Admin syscalls, these are blocked
-//acct
-//adjtimex
-//bdflush
-//chroot
-//create_module
-//delete_module
-//get_kernel_syms      // Obsolete
-//idle                 // Obsolete
-//init_module
-//ioperm
-//iopl
-//ioprio_get
-//ioprio_set
-//kexec_load
-//lookup_dcookie       // oprofile only?
-//migrate_pages        // NUMA
-//modify_ldt
-//mount
-//move_pages           // NUMA
-//name_to_handle_at    // NFS server
-//nfsservctl           // NFS server
-//open_by_handle_at    // NFS server
-//perf_event_open
-//pivot_root
-//process_vm_readv     // For debugger
-//process_vm_writev    // For debugger
-//ptrace               // For debugger
-//query_module
-//quotactl
-//reboot
-//setdomainname
-//sethostname
-//setns
-//settimeofday
-//sgetmask             // Obsolete
-//ssetmask             // Obsolete
-//stime
-//swapoff
-//swapon
-//_sysctl
-//sysfs
-//sys_setaltroot
-//umount
-//umount2
-//unshare
-//uselib
-//vhangup
-//vm86
-//vm86old
-
-// Kernel key management
-//add_key
-//keyctl
-//request_key
-
-// Unimplemented
-//afs_syscall
-//break
-//ftime
-//getpmsg
-//gtty
-//lock
-//madvise1
-//mpx
-//prof
-//profil
-//putpmsg
-//security
-//stty
-//tuxcall
-//ulimit
-//vserver

contrib/udev/80-docker.rules

@@ -1,3 +0,0 @@
-# hide docker's loopback devices from udisks, and thus from user desktops
-SUBSYSTEM=="block", ENV{DM_NAME}=="docker-*", ENV{UDISKS_PRESENTATION_HIDE}="1", ENV{UDISKS_IGNORE}="1"
-SUBSYSTEM=="block", DEVPATH=="/devices/virtual/block/loop*", ATTR{loop/backing_file}=="/var/lib/docker/*", ENV{UDISKS_PRESENTATION_HIDE}="1", ENV{UDISKS_IGNORE}="1"

contrib/vagrant-docker/README.md

@@ -17,34 +17,3 @@ meaning you can use Vagrant to control Docker containers.
 
 * [docker-provider](https://github.com/fgrehm/docker-provider)
 * [vagrant-shell](https://github.com/destructuring/vagrant-shell)
-
-## Setting up Vagrant-docker with the Remote API
-
-The initial Docker upstart script will not work because it runs on `127.0.0.1`, which is not accessible to the host machine. Instead, we need to change the script to connect to `0.0.0.0`. To do this, modify `/etc/init/docker.conf` to look like this:
-
-```
-description     "Docker daemon"
-
-start on filesystem and started lxc-net
-stop on runlevel [!2345]
-
-respawn
-
-script
-    /usr/bin/docker -d -H=tcp://0.0.0.0:4243/
-end script
-```
-
-Once that's done, you need to set up a SSH tunnel between your host machine and the vagrant machine that's running Docker. This can be done by running the following command in a host terminal:
-
-```
-ssh -L 4243:localhost:4243 -p 2222 vagrant@localhost
-```
-
-(The first 4243 is what your host can connect to, the second 4243 is what port Docker is running on in the vagrant machine, and the 2222 is the port Vagrant is providing for SSH. If VirtualBox is the VM you're using, you can see what value "2222" should be by going to: Network > Adapter 1 > Advanced > Port Forwarding in the VirtualBox GUI.)
-
-Note that because the port has been changed, to run docker commands from within the command line you must run them like this:
-
-```
-sudo docker -H 0.0.0.0:4243 < commands for docker >
-```

contrib/zfs/MAINTAINERS

@@ -1 +0,0 @@
-Gurjeet Singh <gurjeet@singh.im> (gurjeet.singh.im)

contrib/zfs/README.md

@@ -1,23 +0,0 @@
-# ZFS Storage Driver
-
-This is a placeholder to declare the presence and status of ZFS storage driver
-for containers.
-
-The current development is done in Gurjeet Singh's fork of Docker, under the
-branch named [zfs_driver].
-
-[zfs_driver]: https://github.com/gurjeet/docker/tree/zfs_driver
-
-
-# Status
-
-Alpha: The code is now capable of creating, running and destroying containers
-and images.
-
-The code is under development. Contributions in the form of suggestions,
-code-reviews, and patches are welcome.
-
-Please send the communication to gurjeet@singh.im and CC at least one Docker
-mailing list.
-
-

docker/docker.go

@@ -23,27 +23,22 @@ func main() {
 		sysinit.SysInit()
 		return
 	}
-
-	var (
-		flVersion            = flag.Bool("v", false, "Print version information and quit")
-		flDaemon             = flag.Bool("d", false, "Enable daemon mode")
-		flDebug              = flag.Bool("D", false, "Enable debug mode")
-		flAutoRestart        = flag.Bool("r", true, "Restart previously running containers")
-		bridgeName           = flag.String("b", "", "Attach containers to a pre-existing network bridge; use 'none' to disable container networking")
-		bridgeIp             = flag.String("bip", "", "Use this CIDR notation address for the network bridge's IP, not compatible with -b")
-		pidfile              = flag.String("p", "/var/run/docker.pid", "Path to use for daemon PID file")
-		flRoot               = flag.String("g", "/var/lib/docker", "Path to use as the root of the docker runtime")
-		flEnableCors         = flag.Bool("api-enable-cors", false, "Enable CORS headers in the remote API")
-		flDns                = docker.NewListOpts(docker.ValidateIp4Address)
-		flEnableIptables     = flag.Bool("iptables", true, "Disable docker's addition of iptables rules")
-		flDefaultIp          = flag.String("ip", "0.0.0.0", "Default IP address to use when binding container ports")
-		flInterContainerComm = flag.Bool("icc", true, "Enable inter-container communication")
-		flGraphDriver        = flag.String("s", "", "Force the docker runtime to use a specific storage driver")
-		flHosts              = docker.NewListOpts(docker.ValidateHost)
-		flMtu                = flag.Int("mtu", docker.DefaultNetworkMtu, "Set the containers network mtu")
-	)
-	flag.Var(&flDns, "dns", "Force docker to use specific DNS servers")
+	// FIXME: Switch d and D ? (to be more sshd like)
+	flVersion := flag.Bool("v", false, "Print version information and quit")
+	flDaemon := flag.Bool("d", false, "Enable daemon mode")
+	flDebug := flag.Bool("D", false, "Enable debug mode")
+	flAutoRestart := flag.Bool("r", true, "Restart previously running containers")
+	bridgeName := flag.String("b", "", "Attach containers to a pre-existing network bridge; use 'none' to disable container networking")
+	pidfile := flag.String("p", "/var/run/docker.pid", "Path to use for daemon PID file")
+	flRoot := flag.String("g", "/var/lib/docker", "Path to use as the root of the docker runtime")
+	flEnableCors := flag.Bool("api-enable-cors", false, "Enable CORS headers in the remote API")
+	flDns := flag.String("dns", "", "Force docker to use specific DNS servers")
+	flHosts := utils.ListOpts{fmt.Sprintf("unix://%s", docker.DEFAULTUNIXSOCKET)}
 	flag.Var(&flHosts, "H", "Multiple tcp://host:port or unix://path/to/socket to bind in daemon mode, single connection otherwise")
+	flEnableIptables := flag.Bool("iptables", true, "Disable docker's addition of iptables rules")
+	flDefaultIp := flag.String("ip", "0.0.0.0", "Default IP address to use when binding container ports")
+	flInterContainerComm := flag.Bool("icc", true, "Enable inter-container communication")
+	flGraphDriver := flag.String("graph-driver", "", "Force docker runtime to use a specific graph driver")
 
 	flag.Parse()
 
@@ -51,18 +46,16 @@ func main() {
 		showVersion()
 		return
 	}
-	if flHosts.Len() == 0 {
-		defaultHost := os.Getenv("DOCKER_HOST")
-
-		if defaultHost == "" || *flDaemon {
-			// If we do not have a host, default to unix socket
-			defaultHost = fmt.Sprintf("unix://%s", docker.DEFAULTUNIXSOCKET)
-		}
-		flHosts.Set(defaultHost)
+	if len(flHosts) > 1 {
+		flHosts = flHosts[1:] //trick to display a nice default value in the usage
 	}
-
-	if *bridgeName != "" && *bridgeIp != "" {
-		log.Fatal("You specified -b & -bip, mutually exclusive options. Please specify only one.")
+	for i, flHost := range flHosts {
+		host, err := utils.ParseHost(docker.DEFAULTHTTPHOST, docker.DEFAULTHTTPPORT, flHost)
+		if err == nil {
+			flHosts[i] = host
+		} else {
+			log.Fatal(err)
+		}
 	}
 
 	if *flDebug {
@@ -75,7 +68,6 @@ func main() {
 			flag.Usage()
 			return
 		}
-
 		eng, err := engine.New(*flRoot)
 		if err != nil {
 			log.Fatal(err)
@@ -86,34 +78,29 @@ func main() {
 		job.Setenv("Root", *flRoot)
 		job.SetenvBool("AutoRestart", *flAutoRestart)
 		job.SetenvBool("EnableCors", *flEnableCors)
-		job.SetenvList("Dns", flDns.GetAll())
+		job.Setenv("Dns", *flDns)
 		job.SetenvBool("EnableIptables", *flEnableIptables)
 		job.Setenv("BridgeIface", *bridgeName)
-		job.Setenv("BridgeIp", *bridgeIp)
 		job.Setenv("DefaultIp", *flDefaultIp)
 		job.SetenvBool("InterContainerCommunication", *flInterContainerComm)
 		job.Setenv("GraphDriver", *flGraphDriver)
-		job.SetenvInt("Mtu", *flMtu)
 		if err := job.Run(); err != nil {
 			log.Fatal(err)
 		}
 		// Serve api
-		job = eng.Job("serveapi", flHosts.GetAll()...)
+		job = eng.Job("serveapi", flHosts...)
 		job.SetenvBool("Logging", true)
 		if err := job.Run(); err != nil {
 			log.Fatal(err)
 		}
 	} else {
-		if flHosts.Len() > 1 {
+		if len(flHosts) > 1 {
 			log.Fatal("Please specify only one -H")
 		}
-		protoAddrParts := strings.SplitN(flHosts.GetAll()[0], "://", 2)
+		protoAddrParts := strings.SplitN(flHosts[0], "://", 2)
 		if err := docker.ParseCommands(protoAddrParts[0], protoAddrParts[1], flag.Args()...); err != nil {
 			if sterr, ok := err.(*utils.StatusError); ok {
-				if sterr.Status != "" {
-					log.Println(sterr.Status)
-				}
-				os.Exit(sterr.StatusCode)
+				os.Exit(sterr.Status)
 			}
 			log.Fatal(err)
 		}

docs/Dockerfile

@@ -9,7 +9,7 @@ run apt-get install -y python-setuptools make
 run easy_install pip
 #from docs/requirements.txt, but here to increase cacheability
 run pip install Sphinx==1.1.3
-run pip install sphinxcontrib-httpdomain==1.1.9
+run pip install sphinxcontrib-httpdomain==1.1.8
 add . /docs
 run cd /docs; make docs
 

docs/MAINTAINERS

@@ -1,4 +1,2 @@
 Andy Rothfusz <andy@dotcloud.com> (@metalivedev)
 Ken Cochrane <ken@dotcloud.com> (@kencochrane)
-James Turnbull <james@lovedthanlost.net> (@jamtur01)
-Sven Dowideit <SvenDowideit@fosiki.com> (@SvenDowideit)

docs/README.md

@@ -41,25 +41,24 @@ its dependencies. There are two main ways to install this tool:
 
 ###Native Installation
 
-Install dependencies from `requirements.txt` file in your `docker/docs`
-directory:
-
-* Linux: `pip install -r docs/requirements.txt`
-
-* Mac OS X: `[sudo] pip-2.7 install -r docs/requirements.txt`
+* Install sphinx: `pip install sphinx`
+    * Mac OS X: `[sudo] pip-2.7 install sphinx`
+* Install sphinx httpdomain contrib package: `pip install sphinxcontrib-httpdomain`
+    * Mac OS X: `[sudo] pip-2.7 install sphinxcontrib-httpdomain`
+* If pip is not available you can probably install it using your favorite package manager as **python-pip**
 
 ###Alternative Installation: Docker Container
 
 If you're running ``docker`` on your development machine then you may
-find it easier and cleaner to use the docs Dockerfile. This installs Sphinx
+find it easier and cleaner to use the Dockerfile. This installs Sphinx
 in a container, adds the local ``docs/`` directory and builds the HTML
 docs inside the container, even starting a simple HTTP server on port
-8000 so that you can connect and see your changes.
+8000 so that you can connect and see your changes. Just run ``docker
+build .`` and run the resulting image. This is the equivalent to
+``make clean server`` since each container starts clean.
 
-In the ``docker`` source directory, run:
-    ```make docs```
-
-This is the equivalent to ``make clean server`` since each container starts clean.
+In the ``docs/`` directory, run:
+    ```docker build -t docker:docs . && docker run -p 8000:8000 docker:docs```
 
 Usage
 -----
@@ -128,8 +127,7 @@ Guides on using sphinx
 
 * Code examples
 
-  * Start typed commands with ``$ `` (dollar space) so that they 
-    are easily differentiated from program output.
+  * Start without $, so it's easy to copy and paste.
   * Use "sudo" with docker to ensure that your command is runnable
     even if they haven't [used the *docker*
     group](http://docs.docker.io/en/latest/use/basics/#why-sudo).
@@ -138,7 +136,7 @@ Manpages
 --------
 
 * To make the manpages, run ``make man``. Please note there is a bug
-  in Sphinx 1.1.3 which makes this fail.  Upgrade to the latest version
+  in spinx 1.1.3 which makes this fail.  Upgrade to the latest version
   of Sphinx.
 * Then preview the manpage by running ``man _build/man/docker.1``,
   where ``_build/man/docker.1`` is the path to the generated manfile

docs/sources/api/docker_remote_api.rst

@@ -26,43 +26,14 @@ Docker Remote API
 2. Versions
 ===========
 
-The current version of the API is 1.8
+The current version of the API is 1.7
 
 Calling /images/<name>/insert is the same as calling
-/v1.8/images/<name>/insert
+/v1.7/images/<name>/insert
 
 You can still call an old version of the api using
 /v1.0/images/<name>/insert
 
-
-v1.8
-****
-
-Full Documentation
-------------------
-
-:doc:`docker_remote_api_v1.8`
-
-What's new
-----------
-
-.. http:post:: /build
-
-   **New!** This endpoint now returns build status as json stream. In case
-   of a build error, it returns the exit status of the failed command.
-
-.. http:get:: /containers/(id)/json
-
-    **New!** This endpoint now returns the host config for the container.
-
-.. http:post:: /images/create
-.. http:post:: /images/(name)/insert
-.. http:post:: /images/(name)/push
-
-  **New!** progressDetail object was added in the JSON. It's now possible
-  to get the current value and the total of the progress without having to
-  parse the string.
-
 v1.7
 ****
 

docs/sources/api/docker_remote_api_v1.3.rst

@@ -1078,7 +1078,7 @@ Monitor Docker's events
 
 	.. sourcecode:: http
 
-           GET /events?since=1374067924
+           POST /events?since=1374067924
 
         **Example response**:
 

docs/sources/api/docker_remote_api_v1.4.rst

@@ -1122,7 +1122,7 @@ Monitor Docker's events
 
 	.. sourcecode:: http
 
-           GET /events?since=1374067924
+           POST /events?since=1374067924
 
         **Example response**:
 

docs/sources/api/docker_remote_api_v1.5.rst

@@ -1093,7 +1093,7 @@ Monitor Docker's events
 
   .. sourcecode:: http
 
-    GET /events?since=1374067924
+    POST /events?since=1374067924
 
   **Example response**:
 

docs/sources/api/docker_remote_api_v1.6.rst

@@ -1228,7 +1228,7 @@ Monitor Docker's events
 
 	.. sourcecode:: http
 
-           GET /events?since=1374067924
+           POST /events?since=1374067924
 
         **Example response**:
 

docs/sources/api/docker_remote_api_v1.7.rst

@@ -122,6 +122,7 @@ Create a container
 		"AttachStdout":true,
 		"AttachStderr":true,
 		"PortSpecs":null,
+		"Privileged": false,
 		"Tty":false,
 		"OpenStdin":false,
 		"StdinOnce":false,
@@ -131,16 +132,12 @@ Create a container
 		],
 		"Dns":null,
 		"Image":"base",
-		"Volumes":{
-			"/tmp": {}
-		},
+		"Volumes":{},
 		"VolumesFrom":"",
-		"WorkingDir":"",
-		"ExposedPorts":{
-			"22/tcp": {}
-		}
-	   }
+		"WorkingDir":""
 
+	   }
+	   
 	**Example response**:
 
 	.. sourcecode:: http
@@ -364,14 +361,9 @@ Start a container
 
            {
                 "Binds":["/tmp:/tmp"],
-                "LxcConf":{"lxc.utsname":"docker"},
-                "PortBindings":{ "22/tcp": [{ "HostPort": "11022" }] },
-                "Privileged":false,
-                "PublishAllPorts":false
+                "LxcConf":{"lxc.utsname":"docker"}
            }
 
-        Binds need to reference Volumes that were defined during container creation.
-
         **Example response**:
 
         .. sourcecode:: http
@@ -998,10 +990,10 @@ Build an image from Dockerfile via stdin
    .. sourcecode:: http
 
       HTTP/1.1 200 OK
-      Content-Type: application/json
 
       {{ STREAM }}
 
+
    The stream must be a tar archive compressed with one of the
    following algorithms: identity (no compression), gzip, bzip2,
    xz. 
@@ -1161,7 +1153,7 @@ Monitor Docker's events
 
 	.. sourcecode:: http
 
-           GET /events?since=1374067924
+           POST /events?since=1374067924
 
         **Example response**:
 

docs/sources/api/registry_api.rst

@@ -19,8 +19,7 @@ Docker Registry API
 - It doesn’t have a local database
 - It will be open-sourced at some point
 
-We expect that there will be multiple registries out there. To help to grasp
-the context, here are some examples of registries:
+We expect that there will be multiple registries out there. To help to grasp the context, here are some examples of registries:
 
 - **sponsor registry**: such a registry is provided by a third-party hosting infrastructure as a convenience for their customers and the docker community as a whole. Its costs are supported by the third party, but the management and operation of the registry are supported by dotCloud. It features read/write access, and delegates authentication and authorization to the Index.
 - **mirror registry**: such a registry is provided by a third-party hosting infrastructure but is targeted at their customers only. Some mechanism (unspecified to date) ensures that public images are pulled from a sponsor registry to the mirror registry, to make sure that the customers of the third-party provider can “docker pull” those images locally.
@@ -38,10 +37,7 @@ the context, here are some examples of registries:
         - local mount point;
         - remote docker addressed through SSH.
 
-The latter would only require two new commands in docker, e.g. ``registryget``
-and ``registryput``, wrapping access to the local filesystem (and optionally
-doing consistency checks). Authentication and authorization are then delegated
-to SSH (e.g. with public keys).
+The latter would only require two new commands in docker, e.g. “registryget” and “registryput”, wrapping access to the local filesystem (and optionally doing consistency checks). Authentication and authorization are then delegated to SSH (e.g. with public keys).
 
 2. Endpoints
 ============

docs/sources/api/registry_index_spec.rst

@@ -15,13 +15,11 @@ Registry & Index Spec
 ---------
 
 The Index is responsible for centralizing information about:
-
 - User accounts
 - Checksums of the images
 - Public namespaces
 
 The Index has different components:
-
 - Web UI
 - Meta-data store (comments, stars, list public repositories)
 - Authentication service
@@ -29,7 +27,7 @@ The Index has different components:
 
 The index is authoritative for those information.
 
-We expect that there will be only one instance of the index, run and managed by Docker Inc.
+We expect that there will be only one instance of the index, run and managed by dotCloud.
 
 1.2 Registry
 ------------
@@ -39,7 +37,7 @@ We expect that there will be only one instance of the index, run and managed by
 - It delegates authentication and authorization to the Index Auth service using tokens
 - It supports different storage backends (S3, cloud files, local FS)
 - It doesn’t have a local database
-- `Source Code <https://github.com/dotcloud/docker-registry>`_
+- It will be open-sourced at some point
 
 We expect that there will be multiple registries out there. To help to grasp the context, here are some examples of registries:
 
@@ -48,6 +46,10 @@ We expect that there will be multiple registries out there. To help to grasp the
 - **vendor registry**: such a registry is provided by a software vendor, who wants to distribute docker images. It would be operated and managed by the vendor. Only users authorized by the vendor would be able to get write access. Some images would be public (accessible for anyone), others private (accessible only for authorized users). Authentication and authorization would be delegated to the Index. The goal of vendor registries is to let someone do “docker pull basho/riak1.3” and automatically push from the vendor registry (instead of a sponsor registry); i.e. get all the convenience of a sponsor registry, while retaining control on the asset distribution.
 - **private registry**: such a registry is located behind a firewall, or protected by an additional security layer (HTTP authorization, SSL client-side certificates, IP address authorization...). The registry is operated by a private entity, outside of dotCloud’s control. It can optionally delegate additional authorization to the Index, but it is not mandatory.
 
+.. note::
+
+    Mirror registries and private registries which do not use the Index don’t even need to run the registry code. They can be implemented by any kind of transport implementing HTTP GET and PUT. Read-only registries can be powered by a simple static HTTP server.
+
 .. note::
 
     The latter implies that while HTTP is the protocol of choice for a registry, multiple schemes are possible (and in some cases, trivial):
@@ -55,16 +57,12 @@ We expect that there will be multiple registries out there. To help to grasp the
         - local mount point;
         - remote docker addressed through SSH.
 
-The latter would only require two new commands in docker, e.g. ``registryget``
-and ``registryput``, wrapping access to the local filesystem (and optionally
-doing consistency checks). Authentication and authorization are then delegated
-to SSH (e.g. with public keys).
+The latter would only require two new commands in docker, e.g. “registryget” and “registryput”, wrapping access to the local filesystem (and optionally doing consistency checks). Authentication and authorization are then delegated to SSH (e.g. with public keys).
 
 1.3 Docker
 ----------
 
 On top of being a runtime for LXC, Docker is the Registry client. It supports:
-
 - Push / Pull on the registry
 - Client authentication on the Index
 
@@ -78,33 +76,21 @@ On top of being a runtime for LXC, Docker is the Registry client. It supports:
 
 1. Contact the Index to know where I should download “samalba/busybox”
 2. Index replies:
-   a. ``samalba/busybox`` is on Registry A
-   b. here are the checksums for ``samalba/busybox`` (for all layers)
+   a. “samalba/busybox” is on Registry A
+   b. here are the checksums for “samalba/busybox” (for all layers)
    c. token
-3. Contact Registry A to receive the layers for ``samalba/busybox`` (all of them to the base image). Registry A is authoritative for “samalba/busybox” but keeps a copy of all inherited layers and serve them all from the same location.
+3. Contact Registry A to receive the layers for “samalba/busybox” (all of them to the base image). Registry A is authoritative for “samalba/busybox” but keeps a copy of all inherited layers and serve them all from the same location.
 4. registry contacts index to verify if token/user is allowed to download images
 5. Index returns true/false lettings registry know if it should proceed or error out
 6. Get the payload for all layers
 
-It's possible to run:
+It’s possible to run docker pull \https://<registry>/repositories/samalba/busybox. In this case, docker bypasses the Index. However the security is not guaranteed (in case Registry A is corrupted) because there won’t be any checksum checks.
 
-.. code-block:: bash
+Currently registry redirects to s3 urls for downloads, going forward all downloads need to be streamed through the registry. The Registry will then abstract the calls to S3 by a top-level class which implements sub-classes for S3 and local storage.
 
-    docker pull https://<registry>/repositories/samalba/busybox
+Token is only returned when the 'X-Docker-Token' header is sent with request.
 
-In this case, Docker bypasses the Index. However the security is not guaranteed
-(in case Registry A is corrupted) because there won’t be any checksum checks.
-
-Currently registry redirects to s3 urls for downloads, going forward all
-downloads need to be streamed through the registry. The Registry will then
-abstract the calls to S3 by a top-level class which implements sub-classes for
-S3 and local storage.
-
-Token is only returned when the ``X-Docker-Token`` header is sent with request.
-
-Basic Auth is required to pull private repos. Basic auth isn't required for
-pulling public repos, but if one is provided, it needs to be valid and for an
-active account.
+Basic Auth is required to pull private repos. Basic auth isn't required for pulling public repos, but if one is provided, it needs to be valid and for an active account.
 
 API (pulling repository foo/bar):
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -173,9 +159,7 @@ API (pulling repository foo/bar):
 
     **Index can be replaced!** For a private Registry deployed, a custom Index can be used to serve and validate token according to different policies.
 
-Docker computes the checksums and submit them to the Index at the end of the
-push. When a repository name does not have checksums on the Index, it means
-that the push is in progress (since checksums are submitted at the end).
+Docker computes the checksums and submit them to the Index at the end of the push. When a repository name does not have checksums on the Index, it means that the push is in progress (since checksums are submitted at the end).
 
 API (pushing repos foo/bar):
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -257,11 +241,10 @@ API (pushing repos foo/bar):
 2.3 Delete
 ----------
 
-If you need to delete something from the index or registry, we need a nice
-clean way to do that. Here is the workflow.
+If you need to delete something from the index or registry, we need a nice clean way to do that. Here is the workflow.
 
-1. Docker contacts the index to request a delete of a repository ``samalba/busybox`` (authentication required with user credentials)
-2. If authentication works and repository is valid, ``samalba/busybox`` is marked as deleted and a temporary token is returned
+1. Docker contacts the index to request a delete of a repository “samalba/busybox” (authentication required with user credentials)
+2. If authentication works and repository is valid, “samalba/busybox” is marked as deleted and a temporary token is returned
 3. Send a delete request to the registry for the repository (along with the token)
 4. Registry A contacts the Index to verify the token (token must corresponds to the repository name)
 5. Index validates the token. Registry A deletes the repository and everything associated to it.
@@ -333,40 +316,24 @@ The Index has two main purposes (along with its fancy social features):
 
 3.1 Without an Index
 --------------------
+Using the Registry without the Index can be useful to store the images on a private network without having to rely on an external entity controlled by dotCloud.
 
-Using the Registry without the Index can be useful to store the images on a
-private network without having to rely on an external entity controlled by
-Docker Inc.
+In this case, the registry will be launched in a special mode (--standalone? --no-index?). In this mode, the only thing which changes is that Registry will never contact the Index to verify a token. It will be the Registry owner responsibility to authenticate the user who pushes (or even pulls) an image using any mechanism (HTTP auth, IP based, etc...).
 
-In this case, the registry will be launched in a special mode (--standalone?
---no-index?). In this mode, the only thing which changes is that Registry will
-never contact the Index to verify a token. It will be the Registry owner
-responsibility to authenticate the user who pushes (or even pulls) an image
-using any mechanism (HTTP auth, IP based, etc...).
+In this scenario, the Registry is responsible for the security in case of data corruption since the checksums are not delivered by a trusted entity.
 
-In this scenario, the Registry is responsible for the security in case of data
-corruption since the checksums are not delivered by a trusted entity.
-
-As hinted previously, a standalone registry can also be implemented by any HTTP
-server handling GET/PUT requests (or even only GET requests if no write access
-is necessary).
+As hinted previously, a standalone registry can also be implemented by any HTTP server handling GET/PUT requests (or even only GET requests if no write access is necessary).
 
 3.2 With an Index
 -----------------
 
 The Index data needed by the Registry are simple:
-
 - Serve the checksums
 - Provide and authorize a Token
 
-In the scenario of a Registry running on a private network with the need of
-centralizing and authorizing, it’s easy to use a custom Index.
+In the scenario of a Registry running on a private network with the need of centralizing and authorizing, it’s easy to use a custom Index.
 
-The only challenge will be to tell Docker to contact (and trust) this custom
-Index. Docker will be configurable at some point to use a specific Index, it’ll
-be the private entity responsibility (basically the organization who uses
-Docker in a private environment) to maintain the Index and the Docker’s
-configuration among its consumers.
+The only challenge will be to tell Docker to contact (and trust) this custom Index. Docker will be configurable at some point to use a specific Index, it’ll be the private entity responsibility (basically the organization who uses Docker in a private environment) to maintain the Index and the Docker’s configuration among its consumers.
 
 4. The API
 ==========
@@ -376,22 +343,16 @@ The first version of the api is available here: https://github.com/jpetazzo/dock
 4.1 Images
 ----------
 
-The format returned in the images is not defined here (for layer and JSON),
-basically because Registry stores exactly the same kind of information as
-Docker uses to manage them.
+The format returned in the images is not defined here (for layer and json), basically because Registry stores exactly the same kind of information as Docker uses to manage them.
 
-The format of ancestry is a line-separated list of image ids, in age order,
-i.e. the image’s parent is on the last line, the parent of the parent on the
-next-to-last line, etc.; if the image has no parent, the file is empty.
+The format of ancestry is a line-separated list of image ids, in age order. I.e. the image’s parent is on the last line, the parent of the parent on the next-to-last line, etc.; if the image has no parent, the file is empty.
 
-.. code-block:: bash
-
-    GET /v1/images/<image_id>/layer
-    PUT /v1/images/<image_id>/layer
-    GET /v1/images/<image_id>/json
-    PUT /v1/images/<image_id>/json
-    GET /v1/images/<image_id>/ancestry
-    PUT /v1/images/<image_id>/ancestry
+GET /v1/images/<image_id>/layer
+PUT /v1/images/<image_id>/layer
+GET /v1/images/<image_id>/json
+PUT /v1/images/<image_id>/json
+GET /v1/images/<image_id>/ancestry
+PUT /v1/images/<image_id>/ancestry
 
 4.2 Users
 ---------
@@ -436,9 +397,7 @@ PUT /v1/users/<username>
 
 4.2.3 Login (Index)
 ^^^^^^^^^^^^^^^^^^^
-
-Does nothing else but asking for a user authentication. Can be used to validate
-credentials. HTTP Basic Auth for now, maybe change in future.
+Does nothing else but asking for a user authentication. Can be used to validate credentials. HTTP Basic Auth for now, maybe change in future.
 
 GET /v1/users
 
@@ -450,10 +409,7 @@ GET /v1/users
 4.3 Tags (Registry)
 -------------------
 
-The Registry does not know anything about users. Even though repositories are
-under usernames, it’s just a namespace for the registry. Allowing us to
-implement organizations or different namespaces per user later, without
-modifying the Registry’s API.
+The Registry does not know anything about users. Even though repositories are under usernames, it’s just a namespace for the registry. Allowing us to implement organizations or different namespaces per user later, without modifying the Registry’s API.
 
 The following naming restrictions apply:
 
@@ -487,10 +443,7 @@ DELETE /v1/repositories/<namespace>/<repo_name>/tags/<tag>
 4.4 Images (Index)
 ------------------
 
-For the Index to “resolve” the repository name to a Registry location, it uses
-the X-Docker-Endpoints header. In other terms, this requests always add a
-``X-Docker-Endpoints`` to indicate the location of the registry which hosts this
-repository.
+For the Index to “resolve” the repository name to a Registry location, it uses the X-Docker-Endpoints header. In other terms, this requests always add a “X-Docker-Endpoints” to indicate the location of the registry which hosts this repository.
 
 4.4.1 Get the images
 ^^^^^^^^^^^^^^^^^^^^^
@@ -535,20 +488,17 @@ Return 202 OK
 ======================
 
 It’s possible to chain Registries server for several reasons:
-
 - Load balancing
 - Delegate the next request to another server
 
-When a Registry is a reference for a repository, it should host the entire
-images chain in order to avoid breaking the chain during the download.
+When a Registry is a reference for a repository, it should host the entire images chain in order to avoid breaking the chain during the download.
 
 The Index and Registry use this mechanism to redirect on one or the other.
 
 Example with an image download:
+On every request, a special header can be returned:
 
-On every request, a special header can be returned::
-
-    X-Docker-Endpoints: server1,server2
+X-Docker-Endpoints: server1,server2
 
 On the next request, the client will always pick a server from this list.
 
@@ -558,8 +508,7 @@ On the next request, the client will always pick a server from this list.
 6.1 On the Index
 -----------------
 
-The Index supports both “Basic” and “Token” challenges. Usually when there is a
-``401 Unauthorized``, the Index replies this::
+The Index supports both “Basic” and “Token” challenges. Usually when there is a “401 Unauthorized”, the Index replies this::
 
     401 Unauthorized
     WWW-Authenticate: Basic realm="auth required",Token
@@ -598,13 +547,11 @@ The Registry only supports the Token challenge::
     401 Unauthorized
     WWW-Authenticate: Token
 
-The only way is to provide a token on ``401 Unauthorized`` responses::
+The only way is to provide a token on “401 Unauthorized” responses::
 
-    Authorization: Token signature=123abc,repository="foo/bar",access=read
+    Authorization: Token signature=123abc,repository=”foo/bar”,access=read
 
-Usually, the Registry provides a Cookie when a Token verification succeeded.
-Every time the Registry passes a Cookie, you have to pass it back the same
-cookie.::
+Usually, the Registry provides a Cookie when a Token verification succeeded. Every time the Registry passes a Cookie, you have to pass it back the same cookie.::
 
     200 OK
     Set-Cookie: session="wD/J7LqL5ctqw8haL10vgfhrb2Q=?foo=UydiYXInCnAxCi4=&timestamp=RjEzNjYzMTQ5NDcuNDc0NjQzCi4="; Path=/; HttpOnly

docs/sources/commandline/cli.rst

@@ -12,58 +12,12 @@ To list available commands, either run ``docker`` with no parameters or execute
 
   $ sudo docker
     Usage: docker [OPTIONS] COMMAND [arg...]
-      -H=[unix:///var/run/docker.sock]: tcp://[host[:port]] to bind/connect to or unix://[/path/to/socket] to use. When host=[0.0.0.0], port=[4243] or path=[/var/run/docker.sock] is omitted, default values are used.
+      -H=[unix:///var/run/docker.sock]: tcp://host:port to bind/connect to or unix://path/to/socket to use
 
     A self-sufficient runtime for linux containers.
 
     ...
 
-.. _cli_daemon:
-
-``daemon``
-----------
-
-::
-
-    Usage of docker:
-      -D=false: Enable debug mode
-      -H=[unix:///var/run/docker.sock]: tcp://[host[:port]] to bind or unix://[/path/to/socket] to use. When host=[0.0.0.0], port=[4243] or path=[/var/run/docker.sock] is omitted, default values are used.
-      -api-enable-cors=false: Enable CORS headers in the remote API
-      -b="": Attach containers to a pre-existing network bridge; use 'none' to disable container networking
-      -bip="": Use the provided CIDR notation address for the dynamically created bridge (docker0); Mutually exclusive of -b
-      -d=false: Enable daemon mode
-      -dns="": Force docker to use specific DNS servers
-      -g="/var/lib/docker": Path to use as the root of the docker runtime
-      -icc=true: Enable inter-container communication
-      -ip="0.0.0.0": Default IP address to use when binding container ports
-      -iptables=true: Disable docker's addition of iptables rules
-      -mtu=1500: Set the containers network mtu
-      -p="/var/run/docker.pid": Path to use for daemon PID file
-      -r=true: Restart previously running containers
-      -s="": Force the docker runtime to use a specific storage driver
-      -v=false: Print version information and quit
-
-The Docker daemon is the persistent process that manages containers.  Docker uses the same binary for both the 
-daemon and client.  To run the daemon you provide the ``-d`` flag.
-
-To force Docker to use devicemapper as the storage driver, use ``docker -d -s devicemapper``.
-
-To set the DNS server for all Docker containers, use ``docker -d -dns 8.8.8.8``.
-
-To run the daemon with debug output, use ``docker -d -D``.
-
-The docker client will also honor the ``DOCKER_HOST`` environment variable to set
-the ``-H`` flag for the client.  
-
-::
- 
-        docker -H tcp://0.0.0.0:4243 ps
-        # or
-        export DOCKER_HOST="tcp://0.0.0.0:4243"
-        docker ps
-        # both are equal
-
-
 .. _cli_attach:
 
 ``attach``
@@ -80,12 +34,11 @@ the ``-H`` flag for the client.
 
 You can detach from the container again (and leave it running) with
 ``CTRL-c`` (for a quiet exit) or ``CTRL-\`` to get a stacktrace of
-the Docker client when it quits.  When you detach from the container's 
-process the exit code will be returned to the client.
+the Docker client when it quits.
 
-To stop a container, use ``docker stop``.
+To stop a container, use ``docker stop``
 
-To kill the container, use ``docker kill``.
+To kill the container, use ``docker kill``
 
 .. _cli_attach_examples:
 
@@ -141,11 +94,12 @@ Examples:
       -no-cache: Do not use the cache when building the image.
       -rm: Remove intermediate containers after a successful build
 
-The files at ``PATH`` or ``URL`` are called the "context" of the build. The
-build process may refer to any of the files in the context, for example when
-using an :ref:`ADD <dockerfile_add>` instruction.  When a single ``Dockerfile``
-is given as ``URL``, then no context is set.  When a Git repository is set as
-``URL``, then the repository is used as the context
+The files at PATH or URL are called the "context" of the build. The
+build process may refer to any of the files in the context, for
+example when using an :ref:`ADD <dockerfile_add>` instruction.  When a
+single ``Dockerfile`` is given as URL, then no context is set.  When a
+git repository is set as URL, then the repository is used as the
+context
 
 .. _cli_build_examples:
 
@@ -156,7 +110,7 @@ Examples:
 
 .. code-block:: bash
 
-    $ sudo docker build .
+    sudo docker build .
     Uploading context 10240 bytes
     Step 1 : FROM busybox
     Pulling repository busybox
@@ -180,13 +134,13 @@ Examples:
      ---> f52f38b7823e
     Successfully built f52f38b7823e
 
-This example specifies that the ``PATH`` is ``.``, and so all the files in
-the local directory get tar'd and sent to the Docker daemon.  The ``PATH``
+This example specifies that the PATH is ``.``, and so all the files in
+the local directory get tar'd and sent to the Docker daemon.  The PATH
 specifies where to find the files for the "context" of the build on
 the Docker daemon. Remember that the daemon could be running on a
-remote machine and that no parsing of the ``Dockerfile`` happens at the
+remote machine and that no parsing of the Dockerfile happens at the
 client side (where you're running ``docker build``). That means that
-*all* the files at ``PATH`` get sent, not just the ones listed to
+*all* the files at PATH get sent, not just the ones listed to
 :ref:`ADD <dockerfile_add>` in the ``Dockerfile``.
 
 The transfer of context from the local machine to the Docker daemon is
@@ -196,7 +150,7 @@ message.
 
 .. code-block:: bash
 
-   $ sudo docker build -t vieux/apache:2.0 .
+   sudo docker build -t vieux/apache:2.0 .
 
 This will build like the previous example, but it will then tag the
 resulting image. The repository name will be ``vieux/apache`` and the
@@ -205,20 +159,20 @@ tag will be ``2.0``
 
 .. code-block:: bash
 
-    $ sudo docker build - < Dockerfile
+    sudo docker build - < Dockerfile
 
 This will read a ``Dockerfile`` from *stdin* without context. Due to
 the lack of a context, no contents of any local directory will be sent
-to the ``docker`` daemon.  Since there is no context, a ``Dockerfile``
+to the ``docker`` daemon.  Since there is no context, a Dockerfile
 ``ADD`` only works if it refers to a remote URL.
 
 .. code-block:: bash
 
-    $ sudo docker build github.com/creack/docker-firefox
+    sudo docker build github.com/creack/docker-firefox
 
-This will clone the GitHub repository and use the cloned repository as
+This will clone the Github repository and use the cloned repository as
 context. The ``Dockerfile`` at the root of the repository is used as
-``Dockerfile``.  Note that you can specify an arbitrary Git repository
+``Dockerfile``.  Note that you can specify an arbitrary git repository
 by using the ``git://`` schema.
 
 
@@ -238,53 +192,28 @@ by using the ``git://`` schema.
       -run="": Configuration to be applied when the image is launched with `docker run`.
                (ex: -run='{"Cmd": ["cat", "/world"], "PortSpecs": ["22"]}')
 
-.. _cli_commit_examples:
-
-Commit an existing container
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+Simple commit of an existing container
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. code-block:: bash
 
-	$ sudo docker ps
+	$ docker ps
 	ID                  IMAGE               COMMAND             CREATED             STATUS              PORTS
 	c3f279d17e0a        ubuntu:12.04        /bin/bash           7 days ago          Up 25 hours                             
 	197387f1b436        ubuntu:12.04        /bin/bash           7 days ago          Up 25 hours                             
 	$ docker commit c3f279d17e0a  SvenDowideit/testimage:version3
 	f5283438590d
 	$ docker images | head
-	REPOSITORY                        TAG                 ID                  CREATED             VIRTUAL SIZE
-	SvenDowideit/testimage            version3            f5283438590d        16 seconds ago      335.7 MB
+	REPOSITORY                        TAG                 ID                  CREATED             SIZE
+	SvenDowideit/testimage            version3            f5283438590d        16 seconds ago      204.2 MB (virtual 335.7 MB)
 	
-Change the command that a container runs
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Sometimes you have an application container running just a service and you need
-to make a quick change and then change it back.
-
-In this example, we run a container with ``ls`` and then change the image to
-run ``ls /etc``.
-
-.. code-block:: bash
-
-        $ docker run -t -name test ubuntu ls
-        bin  boot  dev  etc  home  lib  lib64  media  mnt  opt  proc  root  run  sbin  selinux  srv  sys  tmp  usr  var
-        $ docker commit -run='{"Cmd": ["ls","/etc"]}' test test2
-        933d16de9e70005304c1717b5c6f2f39d6fd50752834c6f34a155c70790011eb
-        $ docker run -t test2
-        adduser.conf            gshadow          login.defs           rc0.d
-        alternatives            gshadow-         logrotate.d          rc1.d
-        apt                     host.conf        lsb-base             rc2.d
-        ...
 
 Full -run example
 .................
 
-The ``-run`` JSON hash changes the ``Config`` section when running ``docker inspect CONTAINERID``
-or ``config`` when running ``docker inspect IMAGEID``.
+(multiline is ok within a single quote ``'``)
 
-(Multiline is okay within a single quote ``'``)
-
-.. code-block:: bash
+::
 
   $ sudo docker commit -run='
   {
@@ -327,7 +256,7 @@ or ``config`` when running ``docker inspect IMAGEID``.
 
     Copy files/folders from the containers filesystem to the host
     path.  Paths are relative to the root of the filesystem.
-
+    
 .. code-block:: bash
 
     $ sudo docker cp 7bb0e258aefe:/etc/debian_version .
@@ -341,7 +270,7 @@ or ``config`` when running ``docker inspect IMAGEID``.
 ::
 
     Usage: docker diff CONTAINER
-
+ 
     List the changed files and directories in a container's filesystem
 
 There are 3 events that are listed in the 'diff':
@@ -350,7 +279,7 @@ There are 3 events that are listed in the 'diff':
 2. ```D``` - Delete
 3. ```C``` - Change
 
-For example:
+for example:
 
 .. code-block:: bash
 
@@ -378,7 +307,7 @@ For example:
     Usage: docker events
 
     Get real time events from the server
-
+    
     -since="": Show previously created events and then stream.
                (either seconds since epoch, or date string as below)
 
@@ -440,13 +369,7 @@ Show events in the past from a specified time
 
     Usage: docker export CONTAINER
 
-    Export the contents of a filesystem as a tar archive to STDOUT
-
-For example:
-
-.. code-block:: bash
-
-    $ sudo docker export red_panda > latest.tar
+    Export the contents of a filesystem as a tar archive
 
 .. _cli_history:
 
@@ -462,7 +385,7 @@ For example:
       -notrunc=false: Don't truncate output
       -q=false: only show numeric IDs
 
-To see how the ``docker:latest`` image was built:
+To see how the docker:latest image was built:
 
 .. code-block:: bash
 
@@ -494,7 +417,7 @@ To see how the ``docker:latest`` image was built:
 	d5e85dc5b1d8        2 weeks ago         /bin/sh -c apt-get update
 	13e642467c11        2 weeks ago         /bin/sh -c echo 'deb http://archive.ubuntu.com/ubuntu precise main universe' > /etc/apt/sources.list
 	ae6dde92a94e        2 weeks ago         /bin/sh -c #(nop) MAINTAINER Solomon Hykes <solomon@dotcloud.com>
-	ubuntu:12.04        6 months ago
+	ubuntu:12.04        6 months ago 
 
 .. _cli_images:
 
@@ -512,23 +435,23 @@ To see how the ``docker:latest`` image was built:
       -q=false: only show numeric IDs
       -tree=false: output graph in tree format
       -viz=false: output graph in graphviz format
-
+      
 Listing the most recently created images
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. code-block:: bash
 
 	$ sudo docker images | head
-	REPOSITORY                    TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
-	<none>                        <none>              77af4d6b9913        19 hours ago        1.089 GB
-	committest                    latest              b6fa739cedf5        19 hours ago        1.089 GB
-	<none>                        <none>              78a85c484f71        19 hours ago        1.089 GB
-	docker                        latest              30557a29d5ab        20 hours ago        1.089 GB
-	<none>                        <none>              0124422dd9f9        20 hours ago        1.089 GB
-	<none>                        <none>              18ad6fad3402        22 hours ago        1.082 GB
-	<none>                        <none>              f9f1e26352f0        23 hours ago        1.089 GB
-	tryout                        latest              2629d1fa0b81        23 hours ago        131.5 MB
-	<none>                        <none>              5ed6274db6ce        24 hours ago        1.089 GB
+	REPOSITORY                    TAG                 IMAGE ID            CREATED             SIZE
+	<none>                        <none>              77af4d6b9913        19 hours ago        30.53 MB (virtual 1.089 GB)
+	committest                    latest              b6fa739cedf5        19 hours ago        30.53 MB (virtual 1.089 GB)
+	<none>                        <none>              78a85c484f71        19 hours ago        30.53 MB (virtual 1.089 GB)
+	docker                        latest              30557a29d5ab        20 hours ago        30.53 MB (virtual 1.089 GB)
+	<none>                        <none>              0124422dd9f9        20 hours ago        30.53 MB (virtual 1.089 GB)
+	<none>                        <none>              18ad6fad3402        22 hours ago        23.68 MB (virtual 1.082 GB)
+	<none>                        <none>              f9f1e26352f0        23 hours ago        30.46 MB (virtual 1.089 GB)
+	tryout                        latest              2629d1fa0b81        23 hours ago        16.4 kB (virtual 131.5 MB)
+	<none>                        <none>              5ed6274db6ce        24 hours ago        30.44 MB (virtual 1.089 GB)
 
 Listing the full length image IDs
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -536,16 +459,16 @@ Listing the full length image IDs
 .. code-block:: bash
 
 	$ sudo docker images -notrunc | head
-	REPOSITORY                    TAG                 IMAGE ID                                                           CREATED             VIRTUAL SIZE
-	<none>                        <none>              77af4d6b9913e693e8d0b4b294fa62ade6054e6b2f1ffb617ac955dd63fb0182   19 hours ago        1.089 GB
-	committest                    latest              b6fa739cedf5ea12a620a439402b6004d057da800f91c7524b5086a5e4749c9f   19 hours ago        1.089 GB
-	<none>                        <none>              78a85c484f71509adeaace20e72e941f6bdd2b25b4c75da8693efd9f61a37921   19 hours ago        1.089 GB
-	docker                        latest              30557a29d5abc51e5f1d5b472e79b7e296f595abcf19fe6b9199dbbc809c6ff4   20 hours ago        1.089 GB
-	<none>                        <none>              0124422dd9f9cf7ef15c0617cda3931ee68346455441d66ab8bdc5b05e9fdce5   20 hours ago        1.089 GB
-	<none>                        <none>              18ad6fad340262ac2a636efd98a6d1f0ea775ae3d45240d3418466495a19a81b   22 hours ago        1.082 GB
-	<none>                        <none>              f9f1e26352f0a3ba6a0ff68167559f64f3e21ff7ada60366e2d44a04befd1d3a   23 hours ago        1.089 GB
-	tryout                        latest              2629d1fa0b81b222fca63371ca16cbf6a0772d07759ff80e8d1369b926940074   23 hours ago        131.5 MB
-	<none>                        <none>              5ed6274db6ceb2397844896966ea239290555e74ef307030ebb01ff91b1914df   24 hours ago        1.089 GB
+	REPOSITORY                    TAG                 IMAGE ID                                                           CREATED             SIZE
+	<none>                        <none>              77af4d6b9913e693e8d0b4b294fa62ade6054e6b2f1ffb617ac955dd63fb0182   19 hours ago        30.53 MB (virtual 1.089 GB)
+	committest                    latest              b6fa739cedf5ea12a620a439402b6004d057da800f91c7524b5086a5e4749c9f   19 hours ago        30.53 MB (virtual 1.089 GB)
+	<none>                        <none>              78a85c484f71509adeaace20e72e941f6bdd2b25b4c75da8693efd9f61a37921   19 hours ago        30.53 MB (virtual 1.089 GB)
+	docker                        latest              30557a29d5abc51e5f1d5b472e79b7e296f595abcf19fe6b9199dbbc809c6ff4   20 hours ago        30.53 MB (virtual 1.089 GB)
+	<none>                        <none>              0124422dd9f9cf7ef15c0617cda3931ee68346455441d66ab8bdc5b05e9fdce5   20 hours ago        30.53 MB (virtual 1.089 GB)
+	<none>                        <none>              18ad6fad340262ac2a636efd98a6d1f0ea775ae3d45240d3418466495a19a81b   22 hours ago        23.68 MB (virtual 1.082 GB)
+	<none>                        <none>              f9f1e26352f0a3ba6a0ff68167559f64f3e21ff7ada60366e2d44a04befd1d3a   23 hours ago        30.46 MB (virtual 1.089 GB)
+	tryout                        latest              2629d1fa0b81b222fca63371ca16cbf6a0772d07759ff80e8d1369b926940074   23 hours ago        16.4 kB (virtual 131.5 MB)
+	<none>                        <none>              5ed6274db6ceb2397844896966ea239290555e74ef307030ebb01ff91b1914df   24 hours ago        30.44 MB (virtual 1.089 GB)
 
 Displaying images visually
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -565,15 +488,15 @@ Displaying image hierarchy
 
     $ sudo docker images -tree
 
-    ├─8dbd9e392a96 Size: 131.5 MB (virtual 131.5 MB) Tags: ubuntu:12.04,ubuntu:latest,ubuntu:precise
+    |─8dbd9e392a96 Size: 131.5 MB (virtual 131.5 MB) Tags: ubuntu:12.04,ubuntu:latest,ubuntu:precise
     └─27cf78414709 Size: 180.1 MB (virtual 180.1 MB)
       └─b750fe79269d Size: 24.65 kB (virtual 180.1 MB) Tags: ubuntu:12.10,ubuntu:quantal
-        ├─f98de3b610d5 Size: 12.29 kB (virtual 180.1 MB)
-        │ └─7da80deb7dbf Size: 16.38 kB (virtual 180.1 MB)
-        │   └─65ed2fee0a34 Size: 20.66 kB (virtual 180.2 MB)
-        │     └─a2b9ea53dddc Size: 819.7 MB (virtual 999.8 MB)
-        │       └─a29b932eaba8 Size: 28.67 kB (virtual 999.9 MB)
-        │         └─e270a44f124d Size: 12.29 kB (virtual 999.9 MB) Tags: progrium/buildstep:latest
+        |─f98de3b610d5 Size: 12.29 kB (virtual 180.1 MB)
+        | └─7da80deb7dbf Size: 16.38 kB (virtual 180.1 MB)
+        |   └─65ed2fee0a34 Size: 20.66 kB (virtual 180.2 MB)
+        |     └─a2b9ea53dddc Size: 819.7 MB (virtual 999.8 MB)
+        |       └─a29b932eaba8 Size: 28.67 kB (virtual 999.9 MB)
+        |         └─e270a44f124d Size: 12.29 kB (virtual 999.9 MB) Tags: progrium/buildstep:latest
         └─17e74ac162d8 Size: 53.93 kB (virtual 180.2 MB)
           └─339a3f56b760 Size: 24.65 kB (virtual 180.2 MB)
             └─904fcc40e34d Size: 96.7 MB (virtual 276.9 MB)
@@ -596,13 +519,13 @@ Displaying image hierarchy
 
     Usage: docker import URL|- [REPOSITORY[:TAG]]
 
-    Create an empty filesystem image and import the contents of the tarball 
-    (.tar, .tar.gz, .tgz, .bzip, .tar.xz, .txz) into it, then optionally tag it.
+    Create a new filesystem image from the contents of a tarball
 
 At this time, the URL must start with ``http`` and point to a single
-file archive (.tar, .tar.gz, .tgz, .bzip, .tar.xz, or .txz) containing a
+file archive (.tar, .tar.gz, .tgz, .bzip, .tar.xz, .txz) containing a
 root filesystem. If you would like to import from a local directory or
-archive, you can use the ``-`` parameter to take the data from *stdin*.
+archive, you can use the ``-`` parameter to take the data from
+standard in.
 
 Examples
 ~~~~~~~~
@@ -612,30 +535,24 @@ Import from a remote location
 
 This will create a new untagged image.
 
-.. code-block:: bash
-
-    $ sudo docker import http://example.com/exampleimage.tgz
+``$ sudo docker import http://example.com/exampleimage.tgz``
 
 Import from a local file
 ........................
 
-Import to docker via pipe and *stdin*.
+Import to docker via pipe and standard in
 
-.. code-block:: bash
-
-    $ cat exampleimage.tgz | sudo docker import - exampleimagelocal:new
+``$ cat exampleimage.tgz | sudo docker import - exampleimagelocal:new``
 
 Import from a local directory
 .............................
 
-.. code-block:: bash
+``$ sudo tar -c . | docker import - exampleimagedir``
 
-    $ sudo tar -c . | docker import - exampleimagedir
-
-Note the ``sudo`` in this example -- you must preserve the ownership of the
-files (especially root ownership) during the archiving with tar. If you are not
-root (or the sudo command) when you tar, then the ownerships might not get
-preserved.
+Note the ``sudo`` in this example -- you must preserve the ownership
+of the files (especially root ownership) during the archiving with
+tar. If you are not root (or sudo) when you tar, then the ownerships
+might not get preserved.
 
 .. _cli_info:
 
@@ -674,22 +591,15 @@ preserved.
 
     Insert a file from URL in the IMAGE at PATH
 
-Use the specified ``IMAGE`` as the parent for a new image which adds a
-:ref:`layer <layer_def>` containing the new file. The ``insert`` command does
-not modify the original image, and the new image has the contents of the parent
-image, plus the new file.
-
-
 Examples
 ~~~~~~~~
 
-Insert file from GitHub
+Insert file from github
 .......................
 
 .. code-block:: bash
 
     $ sudo docker insert 8283e18b24bc https://raw.github.com/metalivedev/django/master/postinstall /tmp/postinstall.sh
-    06fd35556d7b
 
 .. _cli_inspect:
 
@@ -698,55 +608,9 @@ Insert file from GitHub
 
 ::
 
-    Usage: docker inspect CONTAINER|IMAGE [CONTAINER|IMAGE...]
+    Usage: docker inspect [OPTIONS] CONTAINER
 
-    Return low-level information on a container/image
-
-      -format="": Format the output using the given go template.
-
-By default, this will render all results in a JSON array.  If a format
-is specified, the given template will be executed for each result.
-
-Go's `text/template <http://golang.org/pkg/text/template/>`_ package
-describes all the details of the format.
-
-Examples
-~~~~~~~~
-
-Get an instance's IP Address
-............................
-
-For the most part, you can pick out any field from the JSON in a
-fairly straightforward manner.
-
-.. code-block:: bash
-
-    $ sudo docker inspect -format='{{.NetworkSettings.IPAddress}}' $INSTANCE_ID
-
-List All Port Bindings
-......................
-
-One can loop over arrays and maps in the results to produce simple
-text output:
-
-.. code-block:: bash
-
-    $ sudo docker inspect -format='{{range $p, $conf := .NetworkSettings.Ports}} {{$p}} -> {{(index $conf 0).HostPort}} {{end}}' $INSTANCE_ID
-
-Find a Specific Port Mapping
-............................
-
-The ``.Field`` syntax doesn't work when the field name begins with a
-number, but the template language's ``index`` function does.  The
-``.NetworkSettings.Ports`` section contains a map of the internal port
-mappings to a list of external address/port objects, so to grab just
-the numeric public port, you use ``index`` to find the specific port
-map, and then ``index`` 0 contains first object inside of that.  Then
-we ask for the ``HostPort`` field to get the public address.
-
-.. code-block:: bash
-
-    $ sudo docker inspect -format='{{(index (index .NetworkSettings.Ports "8787/tcp") 0).HostPort}}' $INSTANCE_ID
+    Return low-level information on a container
 
 .. _cli_kill:
 
@@ -812,15 +676,6 @@ Known Issues (kill)
 
     Fetch the logs of a container
 
-The ``docker logs`` command is a convenience which batch-retrieves whatever
-logs are present at the time of execution. This does not guarantee execution
-order when combined with a ``docker run`` (i.e. your run may not have generated
-any logs at the time you execute ``docker logs``).
-
-The ``docker logs -f`` command combines ``docker logs`` and ``docker attach``:
-it will first return all logs from the beginning and then continue streaming
-new output from the container's stdout and stderr.
-
 
 .. _cli_port:
 
@@ -849,15 +704,6 @@ new output from the container's stdout and stderr.
       -notrunc=false: Don't truncate output
       -q=false: Only display numeric IDs
 
-Running ``docker ps`` showing 2 linked containers.
-
-.. code-block:: bash
-
-    $ docker ps
-    CONTAINER ID        IMAGE                        COMMAND                CREATED              STATUS              PORTS               NAMES
-    4c01db0b339c        ubuntu:12.04                 bash                   17 seconds ago       Up 16 seconds                           webapp              
-    d7886598dbe2        crosbymichael/redis:latest   /redis-server --dir    33 minutes ago       Up 33 minutes       6379/tcp            redis,webapp/db     
-
 .. _cli_pull:
 
 ``pull``
@@ -906,7 +752,7 @@ Running ``docker ps`` showing 2 linked containers.
         -link="": Remove the link instead of the actual container
 
 Known Issues (rm)
-~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~
 
 * :issue:`197` indicates that ``docker kill`` may leave directories
   behind and make it difficult to remove the container.
@@ -917,7 +763,7 @@ Examples:
 
 .. code-block:: bash
 
-    $ sudo docker rm /redis
+    $ docker rm /redis
     /redis
 
 
@@ -926,7 +772,7 @@ This will remove the container referenced under the link ``/redis``.
 
 .. code-block:: bash
 
-    $ sudo docker rm -link /webapp/redis
+    $ docker rm -link /webapp/redis
     /webapp/redis
 
 
@@ -935,7 +781,7 @@ network communication.
 
 .. code-block:: bash
 
-    $ sudo docker rm `docker ps -a -q`
+    $ docker rm `docker ps -a -q`
 
 
 This command will delete all stopped containers. The command ``docker ps -a -q`` will return all
@@ -952,38 +798,6 @@ containers will not be deleted.
     Usage: docker rmi IMAGE [IMAGE...]
 
     Remove one or more images
-    
-Removing tagged images
-~~~~~~~~~~~~~~~~~~~~~~
-
-Images can be removed either by their short or long ID's, or their image names.
-If an image has more than one name, each of them needs to be removed before the
-image is removed.
-
-.. code-block:: bash
-
-    $ sudo docker images
-    REPOSITORY                TAG                 IMAGE ID            CREATED             SIZE
-    test1                     latest              fd484f19954f        23 seconds ago      7 B (virtual 4.964 MB)
-    test                      latest              fd484f19954f        23 seconds ago      7 B (virtual 4.964 MB)
-    test2                     latest              fd484f19954f        23 seconds ago      7 B (virtual 4.964 MB)
-
-    $ sudo docker rmi fd484f19954f
-    Error: Conflict, cannot delete image fd484f19954f because it is tagged in multiple repositories
-    2013/12/11 05:47:16 Error: failed to remove one or more images
-
-    $ sudo docker rmi test1
-    Untagged: fd484f19954f4920da7ff372b5067f5b7ddb2fd3830cecd17b96ea9e286ba5b8
-    $ sudo docker rmi test2
-    Untagged: fd484f19954f4920da7ff372b5067f5b7ddb2fd3830cecd17b96ea9e286ba5b8
-
-    $ sudo docker images
-    REPOSITORY                TAG                 IMAGE ID            CREATED             SIZE
-    test1                     latest              fd484f19954f        23 seconds ago      7 B (virtual 4.964 MB)
-    $ sudo docker rmi test
-    Untagged: fd484f19954f4920da7ff372b5067f5b7ddb2fd3830cecd17b96ea9e286ba5b8
-    Deleted: fd484f19954f4920da7ff372b5067f5b7ddb2fd3830cecd17b96ea9e286ba5b8
-
 
 .. _cli_run:
 
@@ -1022,39 +836,21 @@ image is removed.
       -name="": Assign the specified name to the container. If no name is specific docker will generate a random name
       -P=false: Publish all exposed ports to the host interfaces
 
-The ``docker run`` command first ``creates`` a writeable container layer over
-the specified image, and then ``starts`` it using the specified command. That
-is, ``docker run`` is equivalent to the API ``/containers/create`` then
-``/containers/(id)/start``.
-
-The ``docker run`` command can be used in combination with ``docker commit`` to
-:ref:`change the command that a container runs <cli_commit_examples>`.
-
-Known Issues (run -volumes-from)
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-* :issue:`2702`: "lxc-start: Permission denied - failed to mount"
-  could indicate a permissions problem with AppArmor. Please see the
-  issue for a workaround.
-
-Examples:
-~~~~~~~~~
+Examples
+--------
 
 .. code-block:: bash
 
-    $ sudo docker run -cidfile /tmp/docker_test.cid ubuntu echo "test"
+    sudo docker run -cidfile /tmp/docker_test.cid ubuntu echo "test"
 
-This will create a container and print ``test`` to the console. The
-``cidfile`` flag makes Docker attempt to create a new file and write the
-container ID to it. If the file exists already, Docker will return an
-error. Docker will close this file when ``docker run`` exits.
+This will create a container and print "test" to the console. The
+``cidfile`` flag makes docker attempt to create a new file and write the
+container ID to it. If the file exists already, docker will return an
+error. Docker will close this file when docker run exits.
 
 .. code-block:: bash
 
-   $ sudo docker run -t -i -rm ubuntu bash
-   root@bc338942ef20:/# mount -t tmpfs none /mnt
-   mount: permission denied
-
+   docker run mount -t tmpfs none /var/spool/squid
 
 This will *not* work, because by default, most potentially dangerous
 kernel capabilities are dropped; including ``cap_sys_admin`` (which is
@@ -1063,12 +859,7 @@ allow it to run:
 
 .. code-block:: bash
 
-   $ sudo docker run -privileged ubuntu bash
-   root@50e3f57e16e6:/# mount -t tmpfs none /mnt
-   root@50e3f57e16e6:/# df -h
-   Filesystem      Size  Used Avail Use% Mounted on
-   none            1.9G     0  1.9G   0% /mnt
-
+   docker run -privileged mount -t tmpfs none /var/spool/squid
 
 The ``-privileged`` flag gives *all* capabilities to the container,
 and it also lifts all the limitations enforced by the ``device``
@@ -1078,15 +869,15 @@ use-cases, like running Docker within Docker.
 
 .. code-block:: bash
 
-   $ sudo docker  run -w /path/to/dir/ -i -t  ubuntu pwd
+   docker  run -w /path/to/dir/ -i -t  ubuntu pwd
 
 The ``-w`` lets the command being executed inside directory given,
-here ``/path/to/dir/``. If the path does not exists it is created inside the
+here /path/to/dir/. If the path does not exists it is created inside the
 container.
 
 .. code-block:: bash
 
-   $ sudo docker  run  -v `pwd`:`pwd` -w `pwd` -i -t  ubuntu pwd
+   docker  run  -v `pwd`:`pwd` -w `pwd` -i -t  ubuntu pwd
 
 The ``-v`` flag mounts the current working directory into the container.
 The ``-w`` lets the command being executed inside the current
@@ -1096,15 +887,15 @@ using the container, but inside the current working directory.
 
 .. code-block:: bash
 
-   $ sudo docker run -p 127.0.0.1:80:8080 ubuntu bash
+    docker run -p 127.0.0.1:80:8080 ubuntu bash
 
-This binds port ``8080`` of the container to port ``80`` on ``127.0.0.1`` of the
+This binds port ``8080`` of the container to port ``80`` on 127.0.0.1 of the
 host machine. :ref:`port_redirection` explains in detail how to manipulate ports
 in Docker.
 
 .. code-block:: bash
 
-    $ sudo docker run -expose 80 ubuntu bash
+    docker run -expose 80 ubuntu bash
 
 This exposes port ``80`` of the container for use within a link without
 publishing the port to the host system's interfaces. :ref:`port_redirection`
@@ -1112,14 +903,14 @@ explains in detail how to manipulate ports in Docker.
 
 .. code-block:: bash
 
-    $ sudo docker run -name console -t -i ubuntu bash
+    docker run -name console -t -i ubuntu bash
 
 This will create and run a new container with the container name
 being ``console``.
 
 .. code-block:: bash
 
-    $ sudo docker run -link /redis:redis -name console ubuntu bash
+    docker run -link /redis:redis -name console ubuntu bash
 
 The ``-link`` flag will link the container named ``/redis`` into the
 newly created container with the alias ``redis``.  The new container
@@ -1129,39 +920,25 @@ to the newly created container.
 
 .. code-block:: bash
 
-   $ sudo docker run -volumes-from 777f7dc92da7,ba8c0c54f0f2:ro -i -t ubuntu pwd
+   docker run -volumes-from 777f7dc92da7,ba8c0c54f0f2:ro -i -t ubuntu pwd
 
 The ``-volumes-from`` flag mounts all the defined volumes from the
-referenced containers. Containers can be specified by a comma seperated
+refrence containers. Containers can be specified by a comma seperated
 list or by repetitions of the ``-volumes-from`` argument. The container
-ID may be optionally suffixed with ``:ro`` or ``:rw`` to mount the volumes in
+id may be optionally suffixed with ``:ro`` or ``:rw`` to mount the volumes in
 read-only or read-write mode, respectively. By default, the volumes are mounted
-in the same mode (read write or read only) as the reference container.
+in the same mode (rw or ro) as the reference container.
 
-A complete example
-..................
-
-.. code-block:: bash
-
-   $ sudo docker run -d -name static static-web-files sh
-   $ sudo docker run -d -expose=8098 -name riak riakserver
-   $ sudo docker run -d -m 100m -e DEVELOPMENT=1 -e BRANCH=example-code -v $(pwd):/app/bin:ro -name app appserver
-   $ sudo docker run -d -p 1443:443 -dns=dns.dev.org -v /var/log/httpd -volumes-from static -link riak -link app -h www.sven.dev.org -name web webserver
-   $ sudo docker run -t -i -rm -volumes-from web -w /var/log/httpd busybox tail -f access.log
-
-This example shows 5 containers that might be set up to test a web application change:
-
-1. Start a pre-prepared volume image ``static-web-files`` (in the background) that has CSS, image and static HTML in it, (with a ``VOLUME`` instruction in the ``Dockerfile`` to allow the web server to use those files);
-2. Start a pre-prepared ``riakserver`` image, give the container name ``riak`` and expose port ``8098`` to any containers that link to it;
-3. Start the ``appserver`` image, restricting its memory usage to 100MB, setting two environment variables ``DEVELOPMENT`` and ``BRANCH`` and bind-mounting the current directory (``$(pwd)``) in the container in read-only mode as ``/app/bin``;
-4. Start the ``webserver``, mapping port ``443`` in the container to port ``1443`` on the Docker server, setting the DNS server to ``dns.dev.org``, creating a volume to put the log files into (so we can access it from another container), then importing the files from the volume exposed by the ``static`` container, and linking to all exposed ports from ``riak`` and ``app``. Lastly, we set the hostname to ``web.sven.dev.org`` so its consistent with the pre-generated SSL certificate;
-5. Finally, we create a container that runs ``tail -f access.log`` using the logs volume from the ``web`` container, setting the workdir to ``/var/log/httpd``. The ``-rm`` option means that when the container exits, the container's layer is removed.
+Known Issues (run -volumes-from)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+* :issue:`2702`: "lxc-start: Permission denied - failed to mount"
+  could indicate a permissions problem with AppArmor. Please see the
+  issue for a workaround.
 
 .. _cli_save:
 
 ``save``
----------
 
 ::
 
@@ -1192,7 +969,7 @@ This example shows 5 containers that might be set up to test a web application c
 
 ::
 
-    Usage: docker start [OPTIONS] CONTAINER
+    Usage: docker start [OPTIONS] NAME
 
     Start a stopped container
 
@@ -1243,7 +1020,7 @@ The main process inside the container will receive SIGTERM, and after a grace pe
 ``version``
 -----------
 
-Show the version of the Docker client, daemon, and latest released version.
+Show the version of the docker client, daemon, and latest released version.
 
 
 .. _cli_wait:

docs/sources/contributing/devenvironment.rst

@@ -42,10 +42,11 @@ This following command will build a development environment using the Dockerfile
 
 .. code-block:: bash
 
-    sudo make build
+    sudo docker build -t docker .
 
-If the build is successful, congratulations! You have produced a clean build of 
-docker, neatly encapsulated in a standard build environment. 
+
+
+If the build is successful, congratulations! You have produced a clean build of docker, neatly encapsulated in a standard build environment. 
 
 
 Step 4: Build the Docker Binary
@@ -55,23 +56,10 @@ To create the Docker binary, run this command:
 
 .. code-block:: bash
 
-	sudo make binary
+	sudo docker run -privileged -v `pwd`:/go/src/github.com/dotcloud/docker docker hack/make.sh binary
 
 This will create the Docker binary in ``./bundles/<version>-dev/binary/``
 
-Using your built Docker binary
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-The binary is available outside the container in the directory 
-``./bundles/<version>-dev/binary/``. You can swap your host docker executable 
-with this binary for live testing - for example, on ubuntu: 
-
-.. code-block:: bash
-
-	sudo service docker stop ; sudo cp $(which docker) $(which docker)_ ; sudo cp ./bundles/<version>-dev/binary/docker-<version>-dev $(which docker);sudo service docker start
-	
-.. note:: Its safer to run the tests below before swapping your hosts docker binary.
-
 
 Step 5: Run the Tests
 ---------------------
@@ -80,15 +68,10 @@ To execute the test cases, run this command:
 
 .. code-block:: bash
 
-	sudo make test
+	sudo docker run -privileged -v `pwd`:/go/src/github.com/dotcloud/docker docker hack/make.sh test
 
 
-Note: if you're running the tests in vagrant, you need to specify a dns entry in 
-the command (either edit the Makefile, or run the step manually): 
-
-.. code-block:: bash
-
-	sudo docker run -dns 8.8.8.8 -privileged -v `pwd`:/go/src/github.com/dotcloud/docker docker hack/make.sh test
+Note: if you're running the tests in vagrant, you need to specify a dns entry in the command: `-dns 8.8.8.8`
 
 If the test are successful then the tail of the output should look something like this
 
@@ -130,24 +113,15 @@ You can run an interactive session in the newly built container:
 
 .. code-block:: bash
 
-	sudo make shell
+	sudo docker run -privileged -i -t docker bash
 
-	# type 'exit' or Ctrl-D to exit
+	# type 'exit' to exit
 
 
-Extra Step: Build and view the Documentation
---------------------------------------------
 
-If you want to read the documentation from a local website, or are making changes
-to it, you can build the documentation and then serve it by:
-
-.. code-block:: bash
-
-	sudo make docs
-    # when its done, you can point your browser to http://yourdockerhost:8000
-	# type Ctrl-C to exit
+.. note:: The binary is available outside the container in the directory  ``./bundles/<version>-dev/binary/``. You can swap your host docker executable with this binary for live testing - for example, on ubuntu: ``sudo service docker stop ; sudo cp $(which docker) $(which docker)_ ; sudo cp ./bundles/<version>-dev/binary/docker-<version>-dev $(which docker);sudo service docker start``.
 
 
 **Need More Help?**
 
-If you need more help then hop on to the `#docker-dev IRC channel <irc://chat.freenode.net#docker-dev>`_ or post a message on the `Docker developer mailing list <https://groups.google.com/d/forum/docker-dev>`_.
+If you need more help then hop on to the `#docker-dev IRC channel <irc://chat.freenode.net#docker-dev>`_ or post a message on the `Docker developer mailinglist <https://groups.google.com/d/forum/docker-dev>`_.

docs/sources/examples/cfengine_process_management.rst

@@ -1,137 +0,0 @@
-:title: Process Management with CFEngine
-:description: Managing containerized processes with CFEngine
-:keywords: cfengine, process, management, usage, docker, documentation
-
-Process Management with CFEngine
-================================
-
-Create Docker containers with managed processes.
-
-Docker monitors one process in each running container and the container lives or dies with that process.
-By introducing CFEngine inside Docker containers, we can alleviate a few of the issues that may arise:
-
-* It is possible to easily start multiple processes within a container, all of which will be managed automatically, with the normal ``docker run`` command.
-* If a managed process dies or crashes, CFEngine will start it again within 1 minute.
-* The container itself will live as long as the CFEngine scheduling daemon (cf-execd) lives. With CFEngine, we are able to decouple the life of the container from the uptime of the service it provides.
-
-
-How it works
-------------
-
-CFEngine, together with the cfe-docker integration policies, are installed as part of the Dockerfile. This builds CFEngine into our Docker image.
-
-The Dockerfile's ``ENTRYPOINT`` takes an arbitrary amount of commands (with any desired arguments) as parameters.
-When we run the Docker container these parameters get written to CFEngine policies and CFEngine takes over to ensure that the desired processes are running in the container.
-
-CFEngine scans the process table for the ``basename`` of the commands given to the ``ENTRYPOINT`` and runs the command to start the process if the ``basename`` is not found.
-For example, if we start the container with ``docker run "/path/to/my/application parameters"``, CFEngine will look for a process named ``application`` and run the command.
-If an entry for ``application`` is not found in the process table at any point in time, CFEngine will execute ``/path/to/my/application parameters`` to start the application once again.
-The check on the process table happens every minute.
-
-Note that it is therefore important that the command to start your application leaves a process with the basename of the command.
-This can be made more flexible by making some minor adjustments to the CFEngine policies, if desired.
-
-
-Usage
------
-
-This example assumes you have Docker installed and working.
-We will install and manage ``apache2`` and ``sshd`` in a single container.
-
-There are three steps:
-
-1. Install CFEngine into the container.
-2. Copy the CFEngine Docker process management policy into the containerized CFEngine installation.
-3. Start your application processes as part of the ``docker run`` command.
-
-
-Building the container image
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-The first two steps can be done as part of a Dockerfile, as follows.
-
-.. code-block:: bash
-
-    FROM ubuntu
-    MAINTAINER Eystein Måløy Stenberg <eytein.stenberg@gmail.com>
-
-    RUN apt-get -y install wget lsb-release unzip
-
-    # install latest CFEngine
-    RUN wget -qO- http://cfengine.com/pub/gpg.key | apt-key add -
-    RUN echo "deb http://cfengine.com/pub/apt $(lsb_release -cs) main" > /etc/apt/sources.list.d/cfengine-community.list
-    RUN apt-get update
-    RUN apt-get install cfengine-community
-
-    # install cfe-docker process management policy
-    RUN wget --no-check-certificate https://github.com/estenberg/cfe-docker/archive/master.zip -P /tmp/ && unzip /tmp/master.zip -d /tmp/
-    RUN cp /tmp/cfe-docker-master/cfengine/bin/* /var/cfengine/bin/
-    RUN cp /tmp/cfe-docker-master/cfengine/inputs/* /var/cfengine/inputs/
-    RUN rm -rf /tmp/cfe-docker-master /tmp/master.zip
-
-    # apache2 and openssh are just for testing purposes, install your own apps here
-    RUN apt-get -y install openssh-server apache2
-    RUN mkdir -p /var/run/sshd
-    RUN echo "root:password" | chpasswd  # need a password for ssh
-
-    ENTRYPOINT ["/var/cfengine/bin/docker_processes_run.sh"]
-
-
-By saving this file as ``Dockerfile`` to a working directory, you can then build your container with the docker build command,
-e.g. ``docker build -t managed_image``.
-
-Testing the container
-~~~~~~~~~~~~~~~~~~~~~
-
-Start the container with ``apache2`` and ``sshd`` running and managed, forwarding a port to our SSH instance:
-
-.. code-block:: bash
-
-    docker run -p 127.0.0.1:222:22 -d managed_image "/usr/sbin/sshd" "/etc/init.d/apache2 start"
-
-We now clearly see one of the benefits of the cfe-docker integration: it allows to start several processes
-as part of a normal ``docker run`` command.
-
-We can now log in to our new container and see that both ``apache2`` and ``sshd`` are running. We have set the root password to
-"password" in the Dockerfile above and can use that to log in with ssh:
-
-.. code-block:: bash
-
-    ssh -p222 root@127.0.0.1
-
-    ps -ef
-    UID        PID  PPID  C STIME TTY          TIME CMD
-    root         1     0  0 07:48 ?        00:00:00 /bin/bash /var/cfengine/bin/docker_processes_run.sh /usr/sbin/sshd /etc/init.d/apache2 start
-    root        18     1  0 07:48 ?        00:00:00 /var/cfengine/bin/cf-execd -F
-    root        20     1  0 07:48 ?        00:00:00 /usr/sbin/sshd
-    root        32     1  0 07:48 ?        00:00:00 /usr/sbin/apache2 -k start
-    www-data    34    32  0 07:48 ?        00:00:00 /usr/sbin/apache2 -k start
-    www-data    35    32  0 07:48 ?        00:00:00 /usr/sbin/apache2 -k start
-    www-data    36    32  0 07:48 ?        00:00:00 /usr/sbin/apache2 -k start
-    root        93    20  0 07:48 ?        00:00:00 sshd: root@pts/0 
-    root       105    93  0 07:48 pts/0    00:00:00 -bash
-    root       112   105  0 07:49 pts/0    00:00:00 ps -ef
-
-
-If we stop apache2, it will be started again within a minute by CFEngine.
-
-.. code-block:: bash
-
-    service apache2 status
-     Apache2 is running (pid 32).
-    service apache2 stop
-             * Stopping web server apache2 ... waiting    [ OK ]
-    service apache2 status
-     Apache2 is NOT running.
-    # ... wait up to 1 minute...
-    service apache2 status
-     Apache2 is running (pid 173).
-
-
-Adapting to your applications
------------------------------
-
-To make sure your applications get managed in the same manner, there are just two things you need to adjust from the above example:
-
-* In the Dockerfile used above, install your applications instead of ``apache2`` and ``sshd``.
-* When you start the container with ``docker run``, specify the command line arguments to your applications rather than ``apache2`` and ``sshd``.

docs/sources/examples/hello_world.rst

@@ -131,6 +131,8 @@ Attach to the container to see the results in real-time.
 
 - **"docker attach**" This will allow us to attach to a background
   process to see what is going on.
+- **"-sig-proxy=true"** Proxify all received signal to the process
+  (even in non-tty mode)
 - **$CONTAINER_ID** The Id of the container we want to attach too.
 
 Exit from the container attachment by pressing Control-C.

docs/sources/examples/index.rst

@@ -24,5 +24,3 @@ to more substantial services like those which you might find in production.
    postgresql_service
    mongodb
    running_riak_service
-   using_supervisord
-   cfengine_process_management

docs/sources/examples/postgresql_service.rst

@@ -7,18 +7,26 @@
 PostgreSQL Service
 ==================
 
-.. include:: example_header.inc
-
 .. note::
 
     A shorter version of `this blog post`_.
 
+.. note::
+
+    As of version 0.5.2, Docker requires root privileges to run.
+    You have to either manually adjust your system configuration (permissions on
+    /var/run/docker.sock or sudo config), or prefix `docker` with `sudo`. Check
+    `this thread`_ for details.
+
 .. _this blog post: http://zaiste.net/2013/08/docker_postgresql_how_to/
+.. _this thread: https://groups.google.com/forum/?fromgroups#!topic/docker-club/P3xDLqmLp0E
 
 Installing PostgreSQL on Docker
 -------------------------------
 
-Run an interactive shell in a Docker container.
+For clarity I won't be showing command output.
+
+Run an interactive shell in Docker container.
 
 .. code-block:: bash
 
@@ -30,26 +38,26 @@ Update its dependencies.
 
     apt-get update
 
-Install ``python-software-properties``, ``software-properties-common``, ``wget`` and ``vim``.
+Install ``python-software-properties``.
 
 .. code-block:: bash
 
-    apt-get -y install python-software-properties software-properties-common wget vim
+    apt-get -y install python-software-properties
+    apt-get -y install software-properties-common
 
-Add PostgreSQL's repository. It contains the most recent stable release
-of PostgreSQL, ``9.3``.
+Add Pitti's PostgreSQL repository. It contains the most recent stable release
+of PostgreSQL i.e. ``9.2``.
 
 .. code-block:: bash
 
-    wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | apt-key add -
-    echo "deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main" > /etc/apt/sources.list.d/pgdg.list
+    add-apt-repository ppa:pitti/postgresql
     apt-get update
 
-Finally, install PostgreSQL 9.3
+Finally, install PostgreSQL 9.2
 
 .. code-block:: bash
 
-    apt-get -y install postgresql-9.3 postgresql-client-9.3 postgresql-contrib-9.3
+    apt-get -y install postgresql-9.2 postgresql-client-9.2 postgresql-contrib-9.2
 
 Now, create a PostgreSQL superuser role that can create databases and
 other roles.  Following Vagrant's convention the role will be named
@@ -68,14 +76,15 @@ role.
 
 Adjust PostgreSQL configuration so that remote connections to the
 database are possible. Make sure that inside
-``/etc/postgresql/9.3/main/pg_hba.conf`` you have following line:
+``/etc/postgresql/9.2/main/pg_hba.conf`` you have following line (you will need
+to install an editor, e.g. ``apt-get install vim``):
 
 .. code-block:: bash
 
     host    all             all             0.0.0.0/0               md5
 
-Additionaly, inside ``/etc/postgresql/9.3/main/postgresql.conf``
-uncomment ``listen_addresses`` like so:
+Additionaly, inside ``/etc/postgresql/9.2/main/postgresql.conf``
+uncomment ``listen_addresses`` so it is as follows:
 
 .. code-block:: bash
 
@@ -85,7 +94,7 @@ uncomment ``listen_addresses`` like so:
 
     This PostgreSQL setup is for development only purposes. Refer
     to PostgreSQL documentation how to fine-tune these settings so that it
-    is secure enough.
+    is enough secure.
 
 Exit.
 
@@ -93,43 +102,43 @@ Exit.
 
     exit
 
-Create an image from our container and assign it a name. The ``<container_id>``
-is in the Bash prompt; you can also locate it using ``docker ps -a``.
+Create an image and assign it a name. ``<container_id>`` is in the
+Bash prompt; you can also locate it using ``docker ps -a``.
 
 .. code-block:: bash
 
     sudo docker commit <container_id> <your username>/postgresql
 
-Finally, run the PostgreSQL server via ``docker``.
+Finally, run PostgreSQL server via ``docker``.
 
 .. code-block:: bash
 
     CONTAINER=$(sudo docker run -d -p 5432 \
       -t <your username>/postgresql \
-      /bin/su postgres -c '/usr/lib/postgresql/9.3/bin/postgres \
-        -D /var/lib/postgresql/9.3/main \
-        -c config_file=/etc/postgresql/9.3/main/postgresql.conf')
+      /bin/su postgres -c '/usr/lib/postgresql/9.2/bin/postgres \
+        -D /var/lib/postgresql/9.2/main \
+        -c config_file=/etc/postgresql/9.2/main/postgresql.conf')
 
-Connect the PostgreSQL server using ``psql`` (You will need the
-postgresql client installed on the machine.  For ubuntu, use something
-like ``sudo apt-get install postgresql-client``).
+Connect the PostgreSQL server using ``psql`` (You will need postgres installed
+on the machine.  For ubuntu, use something like
+``sudo apt-get install postgresql``).
 
 .. code-block:: bash
 
-    CONTAINER_IP=$(sudo docker inspect -format='{{.NetworkSettings.IPAddress}}' $CONTAINER)
+    CONTAINER_IP=$(sudo docker inspect $CONTAINER | grep IPAddress | awk '{ print $2 }' | tr -d ',"')
     psql -h $CONTAINER_IP -p 5432 -d docker -U docker -W
 
 As before, create roles or databases if needed.
 
 .. code-block:: bash
 
-    psql (9.3.1)
+    psql (9.2.4)
     Type "help" for help.
 
     docker=# CREATE DATABASE foo OWNER=docker;
     CREATE DATABASE
 
-Additionally, publish your newly created image on the Docker Index.
+Additionally, publish your newly created image on Docker Index.
 
 .. code-block:: bash
 
@@ -151,9 +160,9 @@ container starts.
 .. code-block:: bash
 
     sudo docker commit -run='{"Cmd": \
-      ["/bin/su", "postgres", "-c", "/usr/lib/postgresql/9.3/bin/postgres -D \
-      /var/lib/postgresql/9.3/main -c \
-      config_file=/etc/postgresql/9.3/main/postgresql.conf"], "PortSpecs": ["5432"]}' \
+      ["/bin/su", "postgres", "-c", "/usr/lib/postgresql/9.2/bin/postgres -D \
+      /var/lib/postgresql/9.2/main -c \
+      config_file=/etc/postgresql/9.2/main/postgresql.conf"], "PortSpecs": ["5432"]}' \
       <container_id> <your username>/postgresql
 
 From now on, just type ``docker run <your username>/postgresql`` and

docs/sources/examples/running_ssh_service.rst

@@ -94,13 +94,5 @@ The password is ``screencast``.
          $ ifconfig
          $ ssh root@192.168.33.10 -p 49154
          # Thanks for watching, Thatcher thatcher@dotcloud.com
-         
-Update:
--------
-
-For Ubuntu 13.10 using stackbrew/ubuntu, you may need do these additional steps:
-
-1. change /etc/pam.d/sshd, pam_loginuid line 'required' to 'optional'
-2. echo LANG=\"en_US.UTF-8\" > /etc/default/locale
 
 

docs/sources/examples/using_supervisord.rst

@@ -1,128 +0,0 @@
-:title: Using Supervisor with Docker
-:description: How to use Supervisor process management with Docker
-:keywords: docker, supervisor, process management
-
-.. _using_supervisord:
-
-Using Supervisor with Docker
-============================
-
-.. include:: example_header.inc
-
-Traditionally a Docker container runs a single process when it is launched, for
-example an Apache daemon or a SSH server daemon. Often though you want to run
-more than one process in a container. There are a number of ways you can
-achieve this ranging from using a simple Bash script as the value of your
-container's ``CMD`` instruction to installing a process management tool.
-
-In this example we're going to make use of the process management tool,
-`Supervisor <http://supervisord.org/>`_, to manage multiple processes in our
-container. Using Supervisor allows us to better control, manage, and restart the
-processes we want to run. To demonstrate this we're going to install and manage both an
-SSH daemon and an Apache daemon.
-
-Creating a Dockerfile
----------------------
-
-Let's start by creating a basic ``Dockerfile`` for our new image.
-
-.. code-block:: bash
-
-    FROM ubuntu:latest
-    MAINTAINER examples@docker.io
-    RUN echo "deb http://archive.ubuntu.com/ubuntu precise main universe" > /etc/apt/sources.list
-    RUN apt-get update
-    RUN apt-get upgrade -y
-
-Installing Supervisor
----------------------
-
-We can now install our SSH and Apache daemons as well as Supervisor in our container.
-
-.. code-block:: bash
-
-    RUN apt-get install -y openssh-server apache2 supervisor
-    RUN mkdir -p /var/run/sshd
-    RUN mkdir -p /var/log/supervisor
-
-Here we're installing the ``openssh-server``, ``apache2`` and ``supervisor``
-(which provides the Supervisor daemon) packages. We're also creating two new
-directories that are needed to run our SSH daemon and Supervisor.
-
-Adding Supervisor's configuration file
---------------------------------------
-
-Now let's add a configuration file for Supervisor. The default file is called
-``supervisord.conf`` and is located in ``/etc/supervisor/conf.d/``.
-
-.. code-block:: bash
-
-    ADD supervisord.conf /etc/supervisor/conf.d/supervisord.conf
-
-Let's see what is inside our ``supervisord.conf`` file.
-
-.. code-block:: bash
-
-    [supervisord]
-    nodaemon=true
-
-    [program:sshd]
-    command=/usr/sbin/sshd -D
-
-    [program:apache2]
-    command=/bin/bash -c "source /etc/apache2/envvars && /usr/sbin/apache2 -DFOREGROUND"
-
-The ``supervisord.conf`` configuration file contains directives that configure
-Supervisor and the processes it manages. The first block ``[supervisord]``
-provides configuration for Supervisor itself. We're using one directive,
-``nodaemon`` which tells Supervisor to run interactively rather than daemonize.
-
-The next two blocks manage the services we wish to control. Each block controls
-a separate process. The blocks contain a single directive, ``command``, which
-specifies what command to run to start each process.
-
-Exposing ports and running Supervisor
--------------------------------------
-
-Now let's finish our ``Dockerfile`` by exposing some required ports and
-specifying the ``CMD`` instruction to start Supervisor when our container
-launches.
-
-.. code-block:: bash
-
-    EXPOSE 22 80
-    CMD ["/usr/bin/supervisord"]
-
-Here we've exposed ports 22 and 80 on the container and we're running the
-``/usr/bin/supervisord`` binary when the container launches.
-
-Building our container
-----------------------
-
-We can now build our new container.
-
-.. code-block:: bash
-
-    sudo docker build -t <yourname>/supervisord .
-
-Running our Supervisor container
---------------------------------
-
-Once we've got a built image we can launch a container from it.
-
-.. code-block:: bash
-
-    sudo docker run -p 22 -p 80 -t -i <yourname>/supervisor
-    2013-11-25 18:53:22,312 CRIT Supervisor running as root (no user in config file)
-    2013-11-25 18:53:22,312 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
-    2013-11-25 18:53:22,342 INFO supervisord started with pid 1
-    2013-11-25 18:53:23,346 INFO spawned: 'sshd' with pid 6
-    2013-11-25 18:53:23,349 INFO spawned: 'apache2' with pid 7
-    . . .
-
-We've launched a new container interactively using the ``docker run`` command.
-That container has run Supervisor and launched the SSH and Apache daemons with
-it. We've specified the ``-p`` flag to expose ports 22 and 80. From here we can
-now identify the exposed ports and connect to one or both of the SSH and Apache
-daemons.
-

docs/sources/faq.rst

@@ -111,7 +111,7 @@ What does Docker add to just plain LXC?
       registry to store and transfer private containers, for internal
       server deployments for example.
 
-   * *Tool ecosystem.*
+   * *Tool ecosystem.* 
       Docker defines an API for automating and customizing the
       creation and deployment of containers. There are a huge number
       of tools integrating with Docker to extend its
@@ -122,11 +122,6 @@ What does Docker add to just plain LXC?
       (Jenkins, Strider, Travis), etc. Docker is rapidly establishing
       itself as the standard for container-based tooling.
 
-What is different between a Docker container and a VM?
-......................................................
-
-There's a great StackOverflow answer `showing the differences <http://stackoverflow.com/questions/16047306/how-is-docker-io-different-from-a-normal-virtual-machine>`_.
-
 Do I lose my data when the container exits?
 ...........................................
 
@@ -134,53 +129,6 @@ Not at all! Any data that your application writes to disk gets preserved
 in its container until you explicitly delete the container. The file
 system for the container persists even after the container halts.
 
-How far do Docker containers scale?
-...................................
-
-Some of the largest server farms in the world today are based on containers.
-Large web deployments like Google and Twitter, and platform providers such as
-Heroku and dotCloud all run on container technology, at a scale of hundreds of
-thousands or even millions of containers running in parallel.
-
-How do I connect Docker containers?
-...................................
-
-Currently the recommended way to link containers is via the `link` primitive.
-You can see details of how to `work with links here
-<http://docs.docker.io/en/latest/use/working_with_links_names/>`_.
-
-Also of useful when enabling more flexible service portability is the
-`Ambassador linking pattern
-<http://docs.docker.io/en/latest/use/ambassador_pattern_linking/>`_.
-
-How do I run more than one process in a Docker container?
-.........................................................
-
-Any capable process supervisor such as http://supervisord.org/, runit, s6, or
-daemontools can do the trick. Docker will start up the process management
-daemon which will then fork to run additional processes. As long as the
-processor manager daemon continues to run, the container will continue to as
-well.  You can see a more substantial example `that uses supervisord here
-<http://docs.docker.io/en/latest/examples/using_supervisord/>`_.
-
-What platforms does Docker run on?
-..................................
-
-Linux:
-
-- Ubuntu 12.04, 13.04 et al
-- Fedora 19/20+
-- RHEL 6.5+
-- Centos 6+
-- Gento
-- ArchLinux
-
-Cloud:
-
-- Amazon EC2
-- Google Compute Engine
-- Rackspace
-
 Can I help by adding some questions and answers?
 ................................................
 

docs/sources/index.rst

@@ -25,7 +25,7 @@ currently in active development, so this documentation will change
 frequently.
 
 For an overview of Docker, please see the `Introduction
-<http://www.docker.io/learn_more/>`_. When you're ready to start working with
+<http://www.docker.io>`_. When you're ready to start working with
 Docker, we have a `quick start <http://www.docker.io/gettingstarted>`_
 and a more in-depth guide to :ref:`ubuntu_linux` and other
 :ref:`installation_list` paths including prebuilt binaries,

docs/sources/installation/amazon.rst

@@ -22,37 +22,20 @@ Amazon QuickStart
 
 1. **Choose an image:**
 
-   * Launch the `Create Instance Wizard
-     <https://console.aws.amazon.com/ec2/v2/home?#LaunchInstanceWizard:>`_ menu
-     on your AWS Console.
-
-   * When picking the source AMI for your instance type, select "Community
-     AMIs".
-
-   * Search for ``amd64 precise``. Pick one of the amd64 Ubuntu images.
-
-   * If you choose a EBS enabled AMI, you'll also be able to launch a
-     ``t1.micro`` instance (more info on `pricing
-     <http://aws.amazon.com/en/ec2/pricing/>`_).  ``t1.micro`` instances are
-     eligible for Amazon's Free Usage Tier.
-
-   * When you click select you'll be taken to the instance setup, and you're one
-     click away from having your Ubuntu VM up and running.
+   * Launch the `Create Instance Wizard` <https://console.aws.amazon.com/ec2/v2/home?#LaunchInstanceWizard:> menu on your AWS Console
+   * Select "Community AMIs" option and serch for ``amd64 precise`` (click enter to search)
+   * If you choose a EBS enabled AMI you will be able to launch a `t1.micro` instance (more info on `pricing` <http://aws.amazon.com/en/ec2/pricing/> )
+   * When you click select you'll be taken to the instance setup, and you're one click away from having your Ubuntu VM up and running.
 
 2. **Tell CloudInit to install Docker:**
 
-   * When you're on the "Configure Instance Details" step, expand the "Advanced
-     Details" section.
+   * Enter ``#include https://get.docker.io`` into the instance *User
+     Data*. `CloudInit <https://help.ubuntu.com/community/CloudInit>`_
+     is part of the Ubuntu image you chose and it bootstraps from this
+     *User Data*.
 
-   * Under "User data", select "As text".
-
-   * Enter ``#include https://get.docker.io`` into the instance *User Data*.
-     `CloudInit <https://help.ubuntu.com/community/CloudInit>`_ is part of the
-     Ubuntu image you chose; it will bootstrap Docker by running the shell
-     script located at this URL.
-
-3. After a few more standard choices where defaults are probably ok, your AWS
-   Ubuntu instance with Docker should be running!
+3. After a few more standard choices where defaults are probably ok, your
+   AWS Ubuntu instance with Docker should be running!
 
 **If this is your first AWS instance, you may need to set up your
 Security Group to allow SSH.** By default all incoming ports to your
@@ -169,7 +152,7 @@ Docker that way too. Vagrant 1.1 or higher is required.
    includes rights to SSH (port 22) to your container.
 
    If you have an advanced AWS setup, you might want to have a look at
-   `vagrant-aws <https://github.com/mitchellh/vagrant-aws>`_.
+   https://github.com/mitchellh/vagrant-aws
 
 7. Connect to your machine
 

docs/sources/installation/archlinux.rst

@@ -1,5 +1,5 @@
 :title: Installation on Arch Linux
-:description: Docker installation on Arch Linux.
+:description: Docker installation on Arch Linux. 
 :keywords: arch linux, virtualization, docker, documentation, installation
 
 .. _arch_linux:
@@ -7,58 +7,54 @@
 Arch Linux
 ==========
 
-.. include:: install_header.inc
+Installing on Arch Linux is not officially supported but can be handled via 
+either of the following AUR packages:
 
-.. include:: install_unofficial.inc
+* `lxc-docker <https://aur.archlinux.org/packages/lxc-docker/>`_
+* `lxc-docker-git <https://aur.archlinux.org/packages/lxc-docker-git/>`_
 
-Installing on Arch Linux can be handled via the package in community:
-
-* `docker <https://www.archlinux.org/packages/community/x86_64/docker/>`_
-
-or the following AUR package:
-
-* `docker-git <https://aur.archlinux.org/packages/docker-git/>`_
-
-The docker package will install the latest tagged version of docker. 
-The docker-git package will build from the current master branch.
+The lxc-docker package will install the latest tagged version of docker. 
+The lxc-docker-git package will build from the current master branch.
 
 Dependencies
 ------------
 
 Docker depends on several packages which are specified as dependencies in
-the packages. The core dependencies are:
+either AUR package.
 
+* aufs3
 * bridge-utils
-* device-mapper
+* go
 * iproute2
+* linux-aufs_friendly
 * lxc
-* sqlite
-
 
 Installation
 ------------
 
-For the normal package a simple
-::
+.. include:: install_header.inc
 
-    pacman -S docker
-    
-is all that is needed.
+.. include:: install_unofficial.inc
 
-For the AUR package execute:
-::
-
-    yaourt -S docker-git
-    
 The instructions here assume **yaourt** is installed.  See 
 `Arch User Repository <https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages>`_
 for information on building and installing packages from the AUR if you have not
 done so before.
 
+Keep in mind that if **linux-aufs_friendly** is not already installed that a
+new kernel will be compiled and this can take quite a while.
+
+::
+
+    yaourt -S lxc-docker-git
+
 
 Starting Docker
 ---------------
 
+Prior to starting docker modify your bootloader to use the 
+**linux-aufs_friendly** kernel and reboot your system.
+
 There is a systemd service unit created for docker.  To start the docker service:
 
 ::

docs/sources/installation/binaries.rst

@@ -12,26 +12,29 @@ Binaries
 **This instruction set is meant for hackers who want to try out Docker
 on a variety of environments.**
 
-Before following these directions, you should really check if a packaged version
-of Docker is already available for your distribution.  We have packages for many
-distributions, and more keep showing up all the time!
+Right now, the officially supported distributions are:
+
+- :ref:`ubuntu_precise`
+- :ref:`ubuntu_raring`
+
+
+But we know people have had success running it under
+
+- Debian
+- Suse
+- :ref:`arch_linux`
 
 Check Your Kernel
 -----------------
 
 Your host's Linux kernel must meet the Docker :ref:`kernel`
 
-Check for User Space Tools
---------------------------
-
-You must have a working installation of the `lxc <http://linuxcontainers.org>`_ utilities and library.
-
 Get the docker binary:
 ----------------------
 
 .. code-block:: bash
 
-    wget https://get.docker.io/builds/Linux/x86_64/docker-latest -O docker
+    wget --output-document=docker https://get.docker.io/builds/Linux/x86_64/docker-latest
     chmod +x docker
 
 

docs/sources/installation/fedora.rst

@@ -1,75 +0,0 @@
-:title: Requirements and Installation on Fedora
-:description: Please note this project is currently under heavy development. It should not be used in production.
-:keywords: Docker, Docker documentation, Fedora, requirements, virtualbox, vagrant, git, ssh, putty, cygwin, linux
-
-.. _fedora:
-
-Fedora
-======
-
-.. include:: install_header.inc
-
-.. include:: install_unofficial.inc
-
-Docker is available in **Fedora 19 and later**. Please note that due to the
-current Docker limitations Docker is able to run only on the **64 bit**
-architecture.
-
-Installation
-------------
-
-The ``docker-io`` package provides Docker on Fedora.
-
-
-If you have the (unrelated) ``docker`` package installed already, it will
-conflict with ``docker-io``. There's a `bug report`_ filed for it.
-To proceed with ``docker-io`` installation on Fedora 19, please remove
-``docker`` first.
-
-.. code-block:: bash
-
-   sudo yum -y remove docker
-
-For Fedora 20 and later, the ``wmdocker`` package will provide the same
-functionality as ``docker`` and will also not conflict with ``docker-io``.
-
-.. code-block:: bash
-
-   sudo yum -y install wmdocker
-   sudo yum -y remove docker
-
-Install the ``docker-io`` package which will install Docker on our host.
-
-.. code-block:: bash
-
-   sudo yum -y install docker-io
-
-
-To update the ``docker-io`` package:
-
-.. code-block:: bash
-
-   sudo yum -y update docker-io
-
-Now that it's installed, let's start the Docker daemon.
-
-.. code-block:: bash
-
-    sudo systemctl start docker
-
-If we want Docker to start at boot, we should also:
-
-.. code-block:: bash
-
-   sudo systemctl enable docker
-
-Now let's verify that Docker is working.
-
-.. code-block:: bash
-
-   sudo docker run -i -t mattdm/fedora /bin/bash
-
-**Done!**, now continue with the :ref:`hello_world` example.
-
-.. _bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1043676
-

docs/sources/installation/frugalware.rst

@@ -1,80 +0,0 @@
-:title: Installation on FrugalWare
-:description: Docker installation on FrugalWare.
-:keywords: frugalware linux, virtualization, docker, documentation, installation
-
-.. _frugalware:
-
-FrugalWare
-==========
-
-.. include:: install_header.inc
-
-.. include:: install_unofficial.inc
-
-Installing on FrugalWare is handled via the official packages:
-
-* `lxc-docker i686 <http://www.frugalware.org/packages/200141>`_
-
-* `lxc-docker x86_64 <http://www.frugalware.org/packages/200130>`_
-
-The `lxc-docker` package will install the latest tagged version of Docker. 
-
-Dependencies
-------------
-
-Docker depends on several packages which are specified as dependencies in
-the packages. The core dependencies are:
-
-* systemd
-* lvm2
-* sqlite3
-* libguestfs
-* lxc
-* iproute2 
-* bridge-utils
-
-
-Installation
-------------
-
-A simple
-::
-
-    pacman -S lxc-docker
-    
-is all that is needed.
-
-
-Starting Docker
----------------
-
-There is a systemd service unit created for Docker.  To start Docker as service:
-
-::
-
-    sudo systemctl start lxc-docker
-
-
-To start on system boot:
-
-::
-
-    sudo systemctl enable lxc-docker
-    
-Network Configuration
----------------------
-
-IPv4 packet forwarding is disabled by default on FrugalWare, so Internet access from inside
-the container may not work.
-
-To enable packet forwarding, run the following command as the ``root`` user on the host system:
-
-::
-
-    sysctl net.ipv4.ip_forward=1
-    
-And, to make it persistent across reboots, add the following to a file named **/etc/sysctl.d/docker.conf**:
-
-::
-
-    net.ipv4.ip_forward=1

docs/sources/installation/gentoolinux.rst

@@ -4,8 +4,8 @@
 
 .. _gentoo_linux:
 
-Gentoo
-======
+Gentoo Linux
+============
 
 .. include:: install_header.inc
 
@@ -22,19 +22,17 @@ provided at https://github.com/tianon/docker-overlay which can be added using
 properly installing and using the overlay can be found in `the overlay README
 <https://github.com/tianon/docker-overlay/blob/master/README.md#using-this-overlay>`_.
 
-Note that sometimes there is a disparity between the latest version and what's
-in the overlay, and between the latest version in the overlay and what's in the
-portage tree.  Please be patient, and the latest version should propagate
-shortly.
-
 Installation
 ^^^^^^^^^^^^
 
 The package should properly pull in all the necessary dependencies and prompt
-for all necessary kernel options.  The ebuilds for 0.7+ include use flags to
-pull in the proper dependencies of the major storage drivers, with the
-"device-mapper" use flag being enabled by default, since that is the simplest
-installation path.
+for all necessary kernel options.  For the most straightforward installation
+experience, use ``sys-kernel/aufs-sources`` as your kernel sources.  If you
+prefer not to use ``sys-kernel/aufs-sources``, the portage tree also contains
+``sys-fs/aufs3``, which includes the patches necessary for adding AUFS support
+to other kernel source packages such as ``sys-kernel/gentoo-sources`` (and a
+``kernel-patch`` USE flag to perform the patching to ``/usr/src/linux``
+automatically).
 
 .. code-block:: bash
 
@@ -49,9 +47,9 @@ the #docker IRC channel on the freenode network.
 Starting Docker
 ^^^^^^^^^^^^^^^
 
-Ensure that you are running a kernel that includes all the necessary modules
-and/or configuration for LXC (and optionally for device-mapper and/or AUFS,
-depending on the storage driver you've decided to use).
+Ensure that you are running a kernel that includes the necessary AUFS
+patches/support and includes all the necessary modules and/or configuration for
+LXC.
 
 OpenRC
 ------

docs/sources/installation/google.rst

@@ -1,73 +0,0 @@
-:title: Installation on Google Cloud Platform
-:description: Please note this project is currently under heavy development. It should not be used in production.
-:keywords: Docker, Docker documentation, installation, google, Google Compute Engine, Google Cloud Platform
-
-`Google Cloud Platform <https://cloud.google.com/>`_
-====================================================
-
-.. include:: install_header.inc
-
-.. _googlequickstart:
-
-`Compute Engine <https://developers.google.com/compute>`_ QuickStart for `Debian <https://www.debian.org>`_
------------------------------------------------------------------------------------------------------------
-
-1. Go to `Google Cloud Console <https://cloud.google.com/console>`_ and create a new Cloud Project with `Compute Engine enabled <https://developers.google.com/compute/docs/signup>`_.
-
-2. Download and configure the `Google Cloud SDK <https://developers.google.com/cloud/sdk/>`_ to use your project with the following commands:
-
-.. code-block:: bash
-
-    $ curl https://dl.google.com/dl/cloudsdk/release/install_google_cloud_sdk.bash | bash
-    $ gcloud auth login
-    Enter a cloud project id (or leave blank to not set): <google-cloud-project-id>
-
-3. Start a new instance, select a zone close to you and the desired instance size:
-
-.. code-block:: bash
-
-    $ gcutil addinstance docker-playground --image=backports-debian-7
-    1: europe-west1-a
-    ...
-    4: us-central1-b
-    >>> <zone-index>
-    1: machineTypes/n1-standard-1
-    ...
-    12: machineTypes/g1-small
-    >>> <machine-type-index>
-
-4. Connect to the instance using SSH:
-
-.. code-block:: bash
-
-    $ gcutil ssh docker-playground
-    docker-playground:~$ 
-
-5. Enable IP forwarding:
-
-.. code-block:: bash
-
-    docker-playground:~$ echo net.ipv4.ip_forward=1 | sudo tee /etc/sysctl.d/99-docker.conf 
-    docker-playground:~$ sudo sysctl --system
-
-6. Install the latest Docker release and configure it to start when the instance boots:
-
-.. code-block:: bash
-
-    docker-playground:~$ curl get.docker.io | bash
-    docker-playground:~$ sudo update-rc.d docker defaults
-
-7. If running in zones: us-central1-a, europe-west1-1, and europe-west1-b, the docker daemon must be started with the `-mtu` flag. Without the flag, you may experience intermittent network pauses. 
-`See this issue <https://code.google.com/p/google-compute-engine/issues/detail?id=57>`_ for more details.
-
-.. code-block:: bash
-
-    docker -d -mtu 1460
-
-8. Start a new container:
-
-.. code-block:: bash
-
-    docker-playground:~$ sudo docker run busybox echo 'docker on GCE \o/'
-    docker on GCE \o/
-

docs/sources/installation/index.rst

@@ -9,7 +9,7 @@ Installation
 
 There are a number of ways to install Docker, depending on where you
 want to run the daemon. The :ref:`ubuntu_linux` installation is the
-officially-tested version. The community adds more techniques for
+officially-tested version, and the community adds more techniques for
 installing Docker all the time.
 
 Contents:
@@ -18,17 +18,13 @@ Contents:
    :maxdepth: 1
 
    ubuntulinux
-   rhel
-   fedora
-   archlinux
-   gentoolinux
-   frugalware
+   binaries
+   security
+   upgrading
+   kernel
    vagrant
    windows
    amazon
    rackspace
-   google
-   kernel
-   binaries
-   security
-   upgrading
+   archlinux
+   gentoolinux

docs/sources/installation/kernel.rst

@@ -11,9 +11,9 @@ In short, Docker has the following kernel requirements:
 
 - Linux version 3.8 or above.
 
-- Cgroups and namespaces must be enabled.
+- `AUFS support <http://aufs.sourceforge.net/>`_.
 
-*Note: as of 0.7 docker no longer requires aufs. AUFS support is still available as an optional driver.*
+- Cgroups and namespaces must be enabled.
 
 The officially supported kernel is the one recommended by the
 :ref:`ubuntu_linux` installation path. It is the one that most developers
@@ -58,6 +58,17 @@ detects something older than 3.8.
 See issue `#407 <https://github.com/dotcloud/docker/issues/407>`_ for details.
 
 
+AUFS support
+------------
+
+Docker currently relies on AUFS, an unioning filesystem.
+While AUFS is included in the kernels built by the Debian and Ubuntu
+distributions, is not part of the standard kernel. This means that if
+you decide to roll your own kernel, you will have to patch your
+kernel tree to add AUFS. The process is documented on
+`AUFS webpage <http://aufs.sourceforge.net/>`_.
+
+
 Cgroups and namespaces
 ----------------------
 
@@ -111,42 +122,3 @@ And replace it by the following one::
     GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1"
 
 Then run ``update-grub``, and reboot.
-
-Details
--------
-
-To automatically check some of the requirements below, you can run `lxc-checkconfig`.
-
-Networking:
-
-- CONFIG_BRIDGE
-- CONFIG_NETFILTER_XT_MATCH_ADDRTYPE
-- CONFIG_NF_NAT
-- CONFIG_NF_NAT_IPV4
-- CONFIG_NF_NAT_NEEDED
-
-LVM:
-
-- CONFIG_BLK_DEV_DM
-- CONFIG_DM_THIN_PROVISIONING
-- CONFIG_EXT4_FS
-
-Namespaces:
-
-- CONFIG_NAMESPACES
-- CONFIG_UTS_NS
-- CONFIG_IPC_NS
-- CONFIG_UID_NS
-- CONFIG_PID_NS
-- CONFIG_NET_NS
-
-Cgroups:
-
-- CONFIG_CGROUPS
-
-Cgroup controllers (optional but highly recommended):
-
-- CONFIG_CGROUP_CPUACCT
-- CONFIG_BLK_CGROUP
-- CONFIG_MEMCG
-- CONFIG_MEMCG_SWAP

docs/sources/installation/rackspace.rst

@@ -2,6 +2,7 @@
 :description: Installing Docker on Ubuntu proviced by Rackspace
 :keywords: Rackspace Cloud, installation, docker, linux, ubuntu
 
+===============
 Rackspace Cloud
 ===============
 
@@ -13,14 +14,14 @@ straightforward, and you should mostly be able to follow the
 
 **However, there is one caveat:**
 
-If you are using any Linux not already shipping with the 3.8 kernel
+If you are using any linux not already shipping with the 3.8 kernel
 you will need to install it. And this is a little more difficult on
 Rackspace.
 
 Rackspace boots their servers using grub's ``menu.lst`` and does not
-like non 'virtual' packages (e.g. Xen compatible) kernels there,
-although they do work. This results in ``update-grub`` not having the
-expected result, and you will need to set the kernel manually.
+like non 'virtual' packages (e.g. xen compatible) kernels there,
+although they do work. This makes ``update-grub`` to not have the
+expected result, and you need to set the kernel manually.
 
 **Do not attempt this on a production machine!**
 
@@ -33,7 +34,7 @@ expected result, and you will need to set the kernel manually.
     apt-get install linux-generic-lts-raring
 
 
-Great, now you have the kernel installed in ``/boot/``, next you need to make it
+Great, now you have kernel installed in ``/boot/``, next is to make it
 boot next time.
 
 .. code-block:: bash
@@ -47,9 +48,9 @@ boot next time.
 Now you need to manually edit ``/boot/grub/menu.lst``, you will find a
 section at the bottom with the existing options.  Copy the top one and
 substitute the new kernel into that. Make sure the new kernel is on
-top, and double check the kernel and initrd lines point to the right files.
+top, and double check kernel and initrd point to the right files.
 
-Take special care to double check the kernel and initrd entries.
+Make special care to double check the kernel and initrd entries.
 
 .. code-block:: bash
 
@@ -78,7 +79,7 @@ It will probably look something like this:
      initrd		/boot/initrd.img-3.2.0-38-virtual
 
 
-Reboot the server (either via command line or console)
+Reboot server (either via command line or console)
 
 .. code-block:: bash
 

docs/sources/installation/rhel.rst

@@ -1,81 +0,0 @@
-:title: Requirements and Installation on Red Hat Enterprise Linux
-:description: Please note this project is currently under heavy development. It should not be used in production.
-:keywords: Docker, Docker documentation, requirements, linux, rhel, centos
-
-.. _rhel:
-
-Red Hat Enterprise Linux 
-========================
-
-.. include:: install_header.inc
-
-.. include:: install_unofficial.inc
-
-Docker is available for **RHEL** on EPEL. These instructions should work for
-both RHEL and CentOS. They will likely work for other binary compatible EL6
-distributions as well, but they haven't been tested.
-
-Please note that this package is part of `Extra Packages for Enterprise
-Linux (EPEL)`_, a community effort to create and maintain additional packages
-for the RHEL distribution.
-
-Also note that due to the current Docker limitations, Docker is able to run
-only on the **64 bit** architecture.
-
-Installation
-------------
-
-Firstly, you need to install the EPEL repository. Please follow the `EPEL installation instructions`_.
-
-
-The ``docker-io`` package provides Docker on EPEL.
-
-
-If you already have the (unrelated) ``docker`` package installed, it will
-conflict with ``docker-io``. There's a `bug report`_ filed for it.
-To proceed with ``docker-io`` installation, please remove
-``docker`` first.
-
-
-Next, let's install the ``docker-io`` package which will install Docker on our host.
-
-.. code-block:: bash
-
-   sudo yum -y install docker-io
-
-To update the ``docker-io`` package
-
-.. code-block:: bash
-
-   sudo yum -y update docker-io
-
-Now that it's installed, let's start the Docker daemon.
-
-.. code-block:: bash
-
-    sudo service docker start
-
-If we want Docker to start at boot, we should also:
-
-.. code-block:: bash
-
-   sudo chkconfig docker on
-
-Now let's verify that Docker is working.
-
-.. code-block:: bash
-
-   sudo docker run -i -t mattdm/fedora /bin/bash
-
-**Done!**, now continue with the :ref:`hello_world` example.
-
-Issues?
--------
-
-If you have any issues - please report them directly in the `Red Hat Bugzilla for docker-io component`_.
-
-.. _Extra Packages for Enterprise Linux (EPEL): https://fedoraproject.org/wiki/EPEL
-.. _EPEL installation instructions: https://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F
-.. _Red Hat Bugzilla for docker-io component : https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL&component=docker-io
-.. _bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1043676
-

docs/sources/installation/ubuntulinux.rst

@@ -4,8 +4,8 @@
 
 .. _ubuntu_linux:
 
-Ubuntu
-======
+Ubuntu Linux
+============
 
 .. warning::
 
@@ -14,11 +14,16 @@ Ubuntu
 
 .. include:: install_header.inc
 
-Docker is supported on the following versions of Ubuntu:
+Right now, the officially supported distribution are:
 
 - :ref:`ubuntu_precise`
 - :ref:`ubuntu_raring`
 
+Docker has the following dependencies
+
+* Linux kernel 3.8 (read more about :ref:`kernel`)
+* AUFS file system support (we are working on BTRFS support as an alternative)
+
 Please read :ref:`ufw`, if you plan to use `UFW (Uncomplicated
 Firewall) <https://help.ubuntu.com/community/UFW>`_
 
@@ -63,48 +68,34 @@ Installation
    These instructions have changed for 0.6. If you are upgrading from
    an earlier version, you will need to follow them again.
 
-Docker is available as a Debian package, which makes installation
-easy. **See the :ref:`installmirrors` section below if you are not in
-the United States.** Other sources of the Debian packages may be
-faster for you to install.
+Docker is available as a Debian package, which makes installation easy.
 
-First add the Docker repository key to your local keychain. You can use the
-``apt-key`` command to check the fingerprint matches: ``36A1 D786 9245 C895 0F96
-6E92 D857 6A8B A88D 21E9``
 
 .. code-block:: bash
 
+   # Add the Docker repository key to your local keychain
+   # using apt-key finger you can check the fingerprint matches 36A1 D786 9245 C895 0F96 6E92 D857 6A8B A88D 21E9
    sudo sh -c "wget -qO- https://get.docker.io/gpg | apt-key add -"
 
-Add the Docker repository to your apt sources list, update and install the
-``lxc-docker`` package.
-
-*You may receive a warning that the package isn't trusted. Answer yes to
-continue installation.*
-
-.. code-block:: bash
-
+   # Add the Docker repository to your apt sources list.
    sudo sh -c "echo deb http://get.docker.io/ubuntu docker main\
    > /etc/apt/sources.list.d/docker.list"
+
+   # Update your sources
    sudo apt-get update
+
+   # Install, you will see another warning that the package cannot be authenticated. Confirm install.
    sudo apt-get install lxc-docker
 
-.. note::
-
-    There is also a simple ``curl`` script available to help with this process.
-
-    .. code-block:: bash
-
-        curl -s https://get.docker.io/ubuntu/ | sudo sh
-
-Now verify that the installation has worked by downloading the ``ubuntu`` image
-and launching a container.
+Verify it worked
 
 .. code-block:: bash
 
+   # download the base 'ubuntu' container and run bash inside it while setting up an interactive shell
    sudo docker run -i -t ubuntu /bin/bash
 
-Type ``exit`` to exit
+   # type 'exit' to exit
+
 
 **Done!**, now continue with the :ref:`hello_world` example.
 
@@ -116,13 +107,10 @@ Ubuntu Raring 13.04 (64 bit)
 Dependencies
 ------------
 
-**Optional AUFS filesystem support**
+**AUFS filesystem support**
 
 Ubuntu Raring already comes with the 3.8 kernel, so we don't need to install it. However, not all systems
-have AUFS filesystem support enabled. AUFS support is optional as of version 0.7, but it's still available as
-a driver and we recommend using it if you can.
-
-To make sure AUFS is installed, run the following commands:
+have AUFS filesystem support enabled, so we need to install it.
 
 .. code-block:: bash
 
@@ -135,37 +123,36 @@ Installation
 
 Docker is available as a Debian package, which makes installation easy.
 
-.. warning::
-
-    Please note that these instructions have changed for 0.6. If you are upgrading from an earlier version, you will need
-    to follow them again.
-
-First add the Docker repository key to your local keychain. You can use the
-``apt-key`` command to check the fingerprint matches: ``36A1 D786 9245 C895 0F96
-6E92 D857 6A8B A88D 21E9``
+*Please note that these instructions have changed for 0.6. If you are upgrading from an earlier version, you will need
+to follow them again.*
 
 .. code-block:: bash
 
+   # Add the Docker repository key to your local keychain
+   # using apt-key finger you can check the fingerprint matches 36A1 D786 9245 C895 0F96 6E92 D857 6A8B A88D 21E9
    sudo sh -c "wget -qO- https://get.docker.io/gpg | apt-key add -"
 
-Add the Docker repository to your apt sources list, update and install the
-``lxc-docker`` package.
-
-.. code-block:: bash
-
+   # Add the Docker repository to your apt sources list.
    sudo sh -c "echo deb http://get.docker.io/ubuntu docker main\
    > /etc/apt/sources.list.d/docker.list"
+
+   # update
    sudo apt-get update
+
+   # install
    sudo apt-get install lxc-docker
 
-Now verify that the installation has worked by downloading the ``ubuntu`` image
-and launching a container.
+
+Verify it worked
 
 .. code-block:: bash
 
+   # download the base 'ubuntu' container
+   # and run bash inside it while setting up an interactive shell
    sudo docker run -i -t ubuntu /bin/bash
 
-Type ``exit`` to exit
+   # type exit to exit
+
 
 **Done!**, now continue with the :ref:`hello_world` example.
 
@@ -175,8 +162,8 @@ Type ``exit`` to exit
 Docker and UFW
 ^^^^^^^^^^^^^^
 
-Docker uses a bridge to manage container networking. By default, UFW drops all
-`forwarding` traffic. As a result will you need to enable UFW forwarding:
+Docker uses a bridge to manage container networking. By default, UFW
+drops all `forwarding`, thus a first step is to enable UFW forwarding:
 
 .. code-block:: bash
 
@@ -194,33 +181,11 @@ Then reload UFW:
    sudo ufw reload
 
 
-UFW's default set of rules denies all `incoming` traffic. If you want to be
-able to reach your containers from another host then you should allow
-incoming connections on the Docker port (default 4243):
+UFW's default set of rules denied all `incoming`, so if you want to be
+able to reach your containers from another host, you should allow
+incoming connections on the docker port (default 4243):
 
 .. code-block:: bash
 
    sudo ufw allow 4243/tcp
 
-.. _installmirrors:
-
-Mirrors
-^^^^^^^
-
-You should ``ping get.docker.io`` and compare the latency to the
-following mirrors, and pick whichever one is best for you.
-
-Yandex
-------
-
-`Yandex <http://yandex.ru/>`_ in Russia is mirroring the Docker Debian
-packages, updating every 6 hours. Substitute
-``http://mirror.yandex.ru/mirrors/docker/`` for
-``http://get.docker.io/ubuntu`` in the instructions above. For example:
-
-.. code-block:: bash
-
-   sudo sh -c "echo deb http://mirror.yandex.ru/mirrors/docker/ docker main\
-   > /etc/apt/sources.list.d/docker.list"
-   sudo apt-get update
-   sudo apt-get install lxc-docker

docs/sources/use/ambassador_pattern_linking.rst

@@ -1,183 +0,0 @@
-:title: Link via an Ambassador Container
-:description: Using the Ambassador pattern to abstract (network) services
-:keywords: Examples, Usage, links, docker, documentation, examples, names, name, container naming
-
-.. _ambassador_pattern_linking:
-
-Link via an Ambassador Container
-================================
-
-Rather than hardcoding network links between a service consumer and provider, Docker
-encourages service portability.
-
-eg, instead of
-
-.. code-block:: bash
-
-	(consumer) --> (redis)
-
-requiring you to restart the ``consumer`` to attach it to a different ``redis`` service, 
-you can add ambassadors
-
-.. code-block:: bash
-
-	(consumer) --> (redis-ambassador) --> (redis)
-
-	or
-
-	(consumer) --> (redis-ambassador) ---network---> (redis-ambassador) --> (redis)
-
-When you need to rewire your consumer to talk to a different redis server, you 
-can just restart the ``redis-ambassador`` container that the consumer is connected to.
-
-This pattern also allows you to transparently move the redis server to a different
-docker host from the consumer.
-
-Using the ``svendowideit/ambassador`` container, the link wiring is controlled entirely 
-from the ``docker run`` parameters.
-
-Two host Example
-----------------
-
-Start actual redis server on one Docker host
-
-.. code-block:: bash
-
-	big-server $ docker run -d -name redis crosbymichael/redis
-
-Then add an ambassador linked to the redis server, mapping a port to the outside world
-
-.. code-block:: bash
-
-	big-server $ docker run -d -link redis:redis -name redis_ambassador -p 6379:6379 svendowideit/ambassador
-
-On the other host, you can set up another ambassador setting environment variables for each remote port we want to proxy to the ``big-server``
-
-.. code-block:: bash
-
-	client-server $ docker run -d -name redis_ambassador -expose 6379 -e REDIS_PORT_6379_TCP=tcp://192.168.1.52:6379 svendowideit/ambassador
-
-Then on the ``client-server`` host, you can use a redis client container to talk 
-to the remote redis server, just by linking to the local redis ambassador.
-
-.. code-block:: bash
-
-	client-server $ docker run -i -t -rm -link redis_ambassador:redis relateiq/redis-cli
-	redis 172.17.0.160:6379> ping
-	PONG
-
-
-
-How it works
-------------
-
-The following example shows what the ``svendowideit/ambassador`` container does 
-automatically (with a tiny amount of ``sed``)
-
-On the docker host (192.168.1.52) that redis will run on:
-
-.. code-block:: bash
-
-	# start actual redis server
-	$ docker run -d -name redis crosbymichael/redis
-
-	# get a redis-cli container for connection testing	
-	$ docker pull relateiq/redis-cli
-
-	# test the redis server by talking to it directly
-	$ docker run -t -i -rm -link redis:redis relateiq/redis-cli
-	redis 172.17.0.136:6379> ping
-	PONG
-	^D
-	
-	# add redis ambassador
-	$ docker run -t -i -link redis:redis -name redis_ambassador -p 6379:6379 busybox sh
-	
-in the redis_ambassador container, you can see the linked redis containers's env
-
-.. code-block:: bash
-
-	$ env
-	REDIS_PORT=tcp://172.17.0.136:6379
-	REDIS_PORT_6379_TCP_ADDR=172.17.0.136
-	REDIS_NAME=/redis_ambassador/redis
-	HOSTNAME=19d7adf4705e
-	REDIS_PORT_6379_TCP_PORT=6379
-	HOME=/
-	REDIS_PORT_6379_TCP_PROTO=tcp
-	container=lxc
-	REDIS_PORT_6379_TCP=tcp://172.17.0.136:6379
-	TERM=xterm
-	PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
-	PWD=/
-	
-	
-This environment is used by the ambassador socat script to expose redis to the world 
-(via the -p 6379:6379 port mapping)
-
-.. code-block:: bash
-
-	$ docker rm redis_ambassador
-	$ sudo ./contrib/mkimage-unittest.sh
-	$ docker run -t -i -link redis:redis -name redis_ambassador -p 6379:6379 docker-ut sh
-	
-	$ socat TCP4-LISTEN:6379,fork,reuseaddr TCP4:172.17.0.136:6379
-	
-then ping the redis server via the ambassador
-
-.. code-block::bash
-
-	$ docker run -i -t -rm -link redis_ambassador:redis relateiq/redis-cli
-	redis 172.17.0.160:6379> ping
-	PONG
-
-Now goto a different server
-
-.. code-block:: bash
-
-	$ sudo ./contrib/mkimage-unittest.sh
-	$ docker run -t -i  -expose 6379 -name redis_ambassador docker-ut sh
-	
-	$ socat TCP4-LISTEN:6379,fork,reuseaddr TCP4:192.168.1.52:6379
-
-and get the redis-cli image so we can talk over the ambassador bridge
-
-.. code-block:: bash
-
-	$ docker pull relateiq/redis-cli
-	$ docker run -i -t -rm -link redis_ambassador:redis relateiq/redis-cli
-	redis 172.17.0.160:6379> ping
-	PONG
-
-The svendowideit/ambassador Dockerfile
---------------------------------------
-
-The ``svendowideit/ambassador`` image is a small busybox image with ``socat`` built in.
-When you start the container, it uses a small ``sed`` script to parse out the (possibly multiple)
-link environment variables to set up the port forwarding. On the remote host, you need to set the 
-variable using the ``-e`` command line option.
-
-``-expose 1234 -e REDIS_PORT_1234_TCP=tcp://192.168.1.52:6379`` will forward the 
-local ``1234`` port to the remote IP and port - in this case ``192.168.1.52:6379``.
-
-
-::
-
-	#
-	#
-	# first you need to build the docker-ut image 
-	# using ./contrib/mkimage-unittest.sh
-	# then 
-	#   docker build -t SvenDowideit/ambassador .
-	#   docker tag SvenDowideit/ambassador ambassador
-	# then to run it (on the host that has the real backend on it)
-	#   docker run -t -i -link redis:redis -name redis_ambassador -p 6379:6379 ambassador
-	# on the remote host, you can set up another ambassador
-	#    docker run -t -i -name redis_ambassador -expose 6379 sh
-
-	FROM	docker-ut
-	MAINTAINER	SvenDowideit@home.org.au
-
-
-	CMD	env | grep _TCP= | sed 's/.*_PORT_\([0-9]*\)_TCP=tcp:\/\/\(.*\):\(.*\)/socat TCP4-LISTEN:\1,fork,reuseaddr TCP4:\2:\3 \&/'  | sh && top
-

docs/sources/use/baseimages.rst

@@ -1,10 +1,10 @@
-:title: Create a Base Image
+:title: Base Image Creation
 :description: How to create base images
 :keywords: Examples, Usage, base image, docker, documentation, examples
 
 .. _base_image_creation:
 
-Create a Base Image
+Base Image Creation
 ===================
 
 So you want to create your own :ref:`base_image_def`? Great!
@@ -37,7 +37,7 @@ There are more example scripts for creating base images in the
 Docker Github Repo:
 
 * `BusyBox <https://github.com/dotcloud/docker/blob/master/contrib/mkimage-busybox.sh>`_
-* `CentOS / Scientific Linux CERN (SLC)
-  <https://github.com/dotcloud/docker/blob/master/contrib/mkimage-rinse.sh>`_
-* `Debian / Ubuntu
+* `CentOS
+  <https://github.com/dotcloud/docker/blob/master/contrib/mkimage-centos.sh>`_
+* `Debian/Ubuntu
   <https://github.com/dotcloud/docker/blob/master/contrib/mkimage-debootstrap.sh>`_

docs/sources/use/basics.rst

@@ -1,15 +1,15 @@
-:title: Learn Basic Commands
+:title: Basic Commands
 :description: Common usage and commands
 :keywords: Examples, Usage, basic commands, docker, documentation, examples
 
 
-Learn Basic Commands
-====================
+The Basics
+==========
 
 Starting Docker
 ---------------
 
-If you have used one of the quick install paths, Docker may have been
+If you have used one of the quick install paths', Docker may have been
 installed with upstart, Ubuntu's system for starting processes at boot
 time. You should be able to run ``sudo docker help`` and get output.
 
@@ -30,8 +30,8 @@ Download a pre-built image
   # Download an ubuntu image
   sudo docker pull ubuntu
 
-This will find the ``ubuntu`` image by name in the :ref:`Central Index
-<searching_central_index>` and download it from the top-level Central
+This will find the ``ubuntu`` image by name in the :ref:`Central Index 
+<searching_central_index>` and download it from the top-level Central 
 Repository to a local image cache.
 
 .. NOTE:: When the image has successfully downloaded, you will see a
@@ -53,23 +53,21 @@ Running an interactive shell
 
 .. _dockergroup:
 
-The sudo command and the docker Group
--------------------------------------
+sudo and the docker Group
+-------------------------
 
-The ``docker`` daemon always runs as the root user, and since Docker version
-0.5.2, the ``docker`` daemon binds to a Unix socket instead of a TCP port. By
-default that Unix socket is owned by the user *root*, and so, by default, you
-can access it with ``sudo``.
+The ``docker`` daemon always runs as root, and since ``docker``
+version 0.5.2, ``docker`` binds to a Unix socket instead of a TCP
+port. By default that Unix socket is owned by the user *root*, and so,
+by default, you can access it with ``sudo``.
 
 Starting in version 0.5.3, if you (or your Docker installer) create a
 Unix group called *docker* and add users to it, then the ``docker``
 daemon will make the ownership of the Unix socket read/writable by the
 *docker* group when the daemon starts. The ``docker`` daemon must
-always run as the root user, but if you run the ``docker`` client as a user in
+always run as root, but if you run the ``docker`` client as a user in
 the *docker* group then you don't need to add ``sudo`` to all the
-client commands.  
-
-.. warning:: The *docker* group is root-equivalent.
+client commands.
 
 **Example:**
 
@@ -78,11 +76,11 @@ client commands.
   # Add the docker group if it doesn't already exist.
   sudo groupadd docker
 
-  # Add the connected user "${USERNAME}" to the docker group.
+  # Add the user "ubuntu" to the docker group.
   # Change the user name to match your preferred user.
   # You may have to logout and log back in again for
   # this to take effect.
-  sudo gpasswd -a ${USERNAME} docker
+  sudo gpasswd -a ubuntu docker
 
   # Restart the docker daemon.
   sudo service docker restart
@@ -99,10 +97,10 @@ Bind Docker to another host/port or a Unix socket
    <https://github.com/dotcloud/docker/issues/1369>`_). Make sure you
    control access to ``docker``.
 
-With ``-H`` it is possible to make the Docker daemon to listen on a
-specific IP and port. By default, it will listen on
+With -H it is possible to make the Docker daemon to listen on a
+specific ip and port. By default, it will listen on
 ``unix:///var/run/docker.sock`` to allow only local connections by the
-*root* user.  You *could* set it to ``0.0.0.0:4243`` or a specific host IP to
+*root* user.  You *could* set it to 0.0.0.0:4243 or a specific host ip to
 give access to everybody, but that is **not recommended** because then
 it is trivial for someone to gain root access to the host where the
 daemon is running.
@@ -181,10 +179,10 @@ Committing (saving) a container state
 
 Save your containers state to a container image, so the state can be re-used.
 
-When you commit your container only the differences between the image the
-container was created from and the current state of the container will be
-stored (as a diff). See which images you already have using the ``docker
-images`` command.
+When you commit your container only the differences between the image
+the container was created from and the current state of the container
+will be stored (as a diff). See which images you already have using
+``sudo docker images``
 
 .. code-block:: bash
 
@@ -196,5 +194,7 @@ images`` command.
 
 You now have a image state from which you can create new instances.
 
+
+
 Read more about :ref:`working_with_the_repository` or continue to the
 complete :ref:`cli`

docs/sources/use/builder.rst

@@ -1,12 +1,12 @@
-:title: Build Images (Dockerfile Reference)
+:title: Dockerfiles for Images
 :description: Dockerfiles use a simple DSL which allows you to automate the steps you would normally manually take to create an image.
 :keywords: builder, docker, Dockerfile, automation, image creation
 
 .. _dockerbuilder:
 
-===================================
-Build Images (Dockerfile Reference)
-===================================
+======================
+Dockerfiles for Images
+======================
 
 **Docker can act as a builder** and read instructions from a text
 ``Dockerfile`` to automate the steps you would otherwise take manually
@@ -251,11 +251,6 @@ All new files and directories are created with mode 0755, uid and gid
    if you build using STDIN (``docker build - < somefile``), there is no build 
    context, so the Dockerfile can only contain an URL based ADD statement.
 
-.. note::
-   if your URL files are protected using authentication, you will need to use
-   an ``RUN wget`` , ``RUN curl`` or other tool from within the container as
-   ADD does not support authentication.
-
 The copy obeys the following rules:
 
 * The ``<src>`` path must be inside the *context* of the build; you cannot 

docs/sources/use/host_integration.rst

@@ -1,11 +1,11 @@
-:title: Automatically Start Containers
+:title: Host Integration
 :description: How to generate scripts for upstart, systemd, etc.
 :keywords: systemd, upstart, supervisor, docker, documentation, host integration
 
 
 
-Automatically Start Containers
-==============================
+Host Integration
+================
 
 You can use your Docker containers with process managers like ``upstart``,
 ``systemd`` and ``supervisor``.

docs/sources/use/index.rst

@@ -17,9 +17,7 @@ Contents:
    workingwithrepository
    baseimages
    port_redirection
-   networking
+   puppet
    host_integration
    working_with_volumes
    working_with_links_names
-   ambassador_pattern_linking
-   puppet

docs/sources/use/networking.rst

@@ -1,153 +0,0 @@
-:title: Configure Networking
-:description: Docker networking
-:keywords: network, networking, bridge, docker, documentation
-
-
-Configure Networking
-====================
-
-Docker uses Linux bridge capabilities to provide network connectivity
-to containers. The ``docker0`` bridge interface is managed by Docker
-itself for this purpose. Thus, when the Docker daemon starts it :
-
-- creates the ``docker0`` bridge if not present
-- searches for an IP address range which doesn't overlap with an existing route
-- picks an IP in the selected range
-- assigns this IP to the ``docker0`` bridge
-
-
-.. code-block:: bash
-    
-    # List host bridges
-    $ sudo brctl show
-    bridge	name	bridge id		STP enabled	interfaces
-    docker0		8000.000000000000	no	
-
-    # Show docker0 IP address
-    $ sudo ifconfig docker0
-    docker0   Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
-   	 inet addr:172.17.42.1  Bcast:0.0.0.0  Mask:255.255.0.0
-
-
-
-At runtime, a :ref:`specific kind of virtual
-interface<vethxxxx-device>` is given to each containers which is then
-bonded to the ``docker0`` bridge.  Each containers also receives a
-dedicated IP address from the same range as ``docker0``. The
-``docker0`` IP address is then used as the default gateway for the
-containers.
-
-.. code-block:: bash
-
-    # Run a container
-    $ sudo docker run -t -i -d base /bin/bash
-    52f811c5d3d69edddefc75aff5a4525fc8ba8bcfa1818132f9dc7d4f7c7e78b4
-
-    $ sudo brctl show
-    bridge	name	bridge id		STP enabled	interfaces
-    docker0		8000.fef213db5a66	no		vethQCDY1N
-
-
-Above, ``docker0`` acts as a bridge for the ``vethQCDY1N`` interface
-which is dedicated to the 52f811c5d3d6 container.
-
-
-How to use a specific IP address range
----------------------------------------
-
-Docker will try hard to find an IP range which is not used by the
-host.  Even if it works for most cases, it's not bullet-proof and
-sometimes you need to have more control over the IP addressing scheme.
-
-For this purpose, Docker allows you to manage the ``docker0`` bridge
-or your own one using the ``-b=<bridgename>`` parameter.
-
-In this scenario:
-
-- ensure Docker is stopped
-- create your own bridge (``bridge0`` for example)
-- assign a specific IP to this bridge
-- start Docker with the ``-b=bridge0`` parameter
-
-
-.. code-block:: bash
-
-    # Stop Docker
-    $ sudo service docker stop
-
-    # Clean docker0 bridge and
-    # add your very own bridge0
-    $ sudo ifconfig docker0 down
-    $ sudo brctl addbr bridge0
-    $ sudo ifconfig bridge0 192.168.227.1 netmask 255.255.255.0
-
-    # Edit your Docker startup file
-    $ echo "DOCKER_OPTS=\"-b=bridge0\"" /etc/default/docker 
-    
-    # Start Docker 
-    $ sudo service docker start
-
-    # Ensure bridge0 IP is not changed by Docker
-    $ sudo ifconfig bridge0
-    bridge0   Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
-              inet addr:192.168.227.1  Bcast:192.168.227.255  Mask:255.255.255.0
-
-    # Run a container
-    $ docker run -i -t base /bin/bash
-
-    # Container IP in the 192.168.227/24 range
-    root@261c272cd7d5:/# ifconfig eth0
-    eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
-              inet addr:192.168.227.5  Bcast:192.168.227.255  Mask:255.255.255.0
-
-    # bridge0 IP as the default gateway
-    root@261c272cd7d5:/# route -n
-    Kernel IP routing table
-    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
-    0.0.0.0         192.168.227.1   0.0.0.0         UG    0      0        0 eth0
-    192.168.227.0   0.0.0.0         255.255.255.0   U     0      0        0 eth0
-
-    # hits CTRL+P then CTRL+Q to detach
-   
-    # Display bridge info 
-    $ sudo brctl show
-    bridge 	name	bridge id		STP enabled	interfaces
-    bridge0		8000.fe7c2e0faebd	no		vethAQI2QT
-    
-    
-Container intercommunication
--------------------------------
-
-Containers can communicate with each other according to the ``icc``
-parameter value of the Docker daemon.
-
-- The default, ``-icc=true`` allows containers to communicate with each other.
-- ``-icc=false`` means containers are isolated from each other.
-
-Under the hood, ``iptables`` is used by Docker to either accept or
-drop communication between containers.
-
-
-.. _vethxxxx-device:
-
-What's about the vethXXXX device?
------------------------------------
-Well. Things get complicated here.
-
-The ``vethXXXX`` interface is the host side of a point-to-point link
-between the host and the corresponding container, the other side of
-the link being materialized by the container's ``eth0``
-interface. This pair (host ``vethXXX`` and container ``eth0``) are
-connected like a tube. Everything that comes in one side will come out
-the other side.
-
-All the plumbing is delegated to Linux network capabilities (check the
-ip link command) and the namespaces infrastructure.
-
-
-I want more
-------------
-
-Jérôme Petazzoni has create ``pipework`` to connect together
-containers in arbitrarily complex scenarios :
-https://github.com/jpetazzo/pipework

docs/sources/use/port_redirection.rst

@@ -1,12 +1,12 @@
-:title: Redirect Ports
+:title: Port redirection
 :description: usage about port redirection
 :keywords: Usage, basic port, docker, documentation, examples
 
 
 .. _port_redirection:
 
-Redirect Ports
-==============
+Port redirection
+================
 
 Interacting with a service is commonly done through a connection to a
 port. When this service runs inside a container, one can connect to
@@ -31,7 +31,7 @@ container, Docker provide ways to bind the container port to an
 interface of the host system. To simplify communication between
 containers, Docker provides the linking mechanism.
 
-Binding a port to a host interface
+Binding a port to an host interface
 -----------------------------------
 
 To bind a port of the container to a specific interface of the host

docs/sources/use/working_with_links_names.rst

@@ -1,16 +1,15 @@
-:title: Link Containers
-:description: How to create and use both links and names
-:keywords: Examples, Usage, links, linking, docker, documentation, examples, names, name, container naming
+:title: Working with Links and Names
+:description: How to create and use links and names
+:keywords: Examples, Usage, links, docker, documentation, examples, names, name, container naming
 
 .. _working_with_links_names:
 
-Link Containers
-===============
+Working with Links and Names
+============================
 
-From version 0.6.5 you are now able to ``name`` a container and
-``link`` it to another container by referring to its name. This will
-create a parent -> child relationship where the parent container can
-see selected information about its child.
+From version 0.6.5 you are now able to ``name`` a container and ``link`` it to another
+container by referring to its name. This will create a parent -> child relationship
+where the parent container can see selected information about its child.
 
 .. _run_name:
 
@@ -19,9 +18,8 @@ Container Naming
 
 .. versionadded:: v0.6.5
 
-You can now name your container by using the ``-name`` flag. If no
-name is provided, Docker will automatically generate a name. You can
-see this name using the ``docker ps`` command.
+You can now name your container by using the ``-name`` flag. If no name is provided, Docker
+will automatically generate a name. You can see this name using the ``docker ps`` command.
 
 .. code-block:: bash
 
@@ -40,53 +38,47 @@ Links: service discovery for docker
 
 .. versionadded:: v0.6.5
 
-Links allow containers to discover and securely communicate with each
-other by using the flag ``-link name:alias``. Inter-container
-communication can be disabled with the daemon flag
-``-icc=false``. With this flag set to ``false``, Container A cannot
-access Container B unless explicitly allowed via a link. This is a
-huge win for securing your containers.  When two containers are linked
-together Docker creates a parent child relationship between the
-containers. The parent container will be able to access information
-via environment variables of the child such as name, exposed ports, IP
-and other selected environment variables.
+Links allow containers to discover and securely communicate with each other by using the
+flag ``-link name:alias``. Inter-container communication can be disabled with the daemon
+flag ``-icc=false``. With this flag set to false, Container A cannot access Container B
+unless explicitly allowed via a link. This is a huge win for securing your containers.
+When two containers are linked together Docker creates a parent child relationship
+between the containers. The parent container will be able to access information via
+environment variables of the child such as name, exposed ports, IP and other selected
+environment variables.
 
-When linking two containers Docker will use the exposed ports of the
-container to create a secure tunnel for the parent to access. If a
-database container only exposes port 8080 then the linked container
-will only be allowed to access port 8080 and nothing else if
+When linking two containers Docker will use the exposed ports of the container to create
+a secure tunnel for the parent to access. If a database container only exposes port 8080
+then the linked container will only be allowed to access port 8080 and nothing else if
 inter-container communication is set to false.
 
-For example, there is an image called ``crosbymichael/redis`` that exposes the
-port 6379 and starts the Redis server. Let's name the container as ``redis``
-based on that image and run it as daemon.
-
-.. code-block:: bash
-
-    $ sudo docker run -d -name redis crosbymichael/redis
-
-We can issue all the commands that you would expect using the name
-``redis``; start, stop, attach, using the name for our container. The
-name also allows us to link other containers into this one.
-
-Next, we can start a new web application that has a dependency on
-Redis and apply a link to connect both containers. If you noticed when
-running our Redis server we did not use the ``-p`` flag to publish the
-Redis port to the host system. Redis exposed port 6379 and this is all
-we need to establish a link.
+.. code-block:: bash
+
+    # Example: there is an image called redis-2.6 that exposes the port 6379 and starts redis-server.
+    # Let's name the container as "redis" based on that image and run it as daemon.
+    $ sudo docker run -d -name redis redis-2.6
+
+We can issue all the commands that you would expect using the name "redis"; start, stop,
+attach, using the name for our container. The name also allows us to link other containers
+into this one.
+
+Next, we can start a new web application that has a dependency on Redis and apply a link
+to connect both containers. If you noticed when running our Redis server we did not use
+the -p flag to publish the Redis port to the host system. Redis exposed port 6379 and
+this is all we need to establish a link.
 
 .. code-block:: bash
 
+    # Linking the redis container as a child
     $ sudo docker run -t -i -link redis:db -name webapp ubuntu bash
 
-When you specified ``-link redis:db`` you are telling Docker to link
-the container named ``redis`` into this new container with the alias
-``db``. Environment variables are prefixed with the alias so that the
-parent container can access network and environment information from
-the containers that are linked into it.
+When you specified -link redis:db you are telling docker to link the container named redis
+into this new container with the alias db. Environment variables are prefixed with the alias
+so that the parent container can access network and environment information from the containers
+that are linked into it.
 
-If we inspect the environment variables of the second container, we
-would see all the information about the child container.
+If we inspect the environment variables of the second container, we would see all the information
+about the child container.
 
 .. code-block:: bash
 
@@ -108,17 +100,5 @@ would see all the information about the child container.
     _=/usr/bin/env
     root@4c01db0b339c:/#
 
-Accessing the network information along with the environment of the
-child container allows us to easily connect to the Redis service on
-the specific IP and port in the environment.
-
-Running ``docker ps`` shows the 2 containers, and the ``webapp/db``
-alias name for the redis container.
-
-.. code-block:: bash
-
-    $ docker ps
-    CONTAINER ID        IMAGE                        COMMAND                CREATED              STATUS              PORTS               NAMES
-    4c01db0b339c        ubuntu:12.04                 bash                   17 seconds ago       Up 16 seconds                           webapp
-    d7886598dbe2        crosbymichael/redis:latest   /redis-server --dir    33 minutes ago       Up 33 minutes       6379/tcp            redis,webapp/db
-
+Accessing the network information along with the environment of the child container allows
+us to easily connect to the Redis service on the specific IP and port in the environment.

docs/sources/use/working_with_volumes.rst

@@ -1,11 +1,11 @@
-:title: Share Directories via Volumes
+:title: Working with Volumes
 :description: How to create and share volumes
 :keywords: Examples, Usage, volume, docker, documentation, examples
 
 .. _volume_def:
 
-Share Directories via Volumes
-=============================
+Data Volume
+===========
 
 .. versionadded:: v0.3.0
    Data volumes have been available since version 1 of the
@@ -13,7 +13,7 @@ Share Directories via Volumes
 
 A *data volume* is a specially-designated directory within one or more
 containers that bypasses the :ref:`ufs_def` to provide several useful
-features for persistent or shared data:
+features for persistant or shared data:
 
 * **Data volumes can be shared and reused between containers.** This
   is the feature that makes data volumes so powerful. You can use it
@@ -30,58 +30,35 @@ Each container can have zero or more data volumes.
 Getting Started
 ...............
 
-Using data volumes is as simple as adding a ``-v`` parameter to the ``docker run`` 
-command. The ``-v`` parameter can be used more than once in order to 
-create more volumes within the new container. To create a new container with 
-two new volumes::
+Using data volumes is as simple as adding a new flag: ``-v``. The
+parameter ``-v`` can be used more than once in order to create more
+volumes within the new container. The example below shows the
+instruction to create a container with two new volumes::
 
-  $ docker run -v /var/volume1 -v /var/volume2 busybox true
+  docker run -v /var/volume1 -v /var/volume2 shykes/couchdb
 
-This command will create the new container with two new volumes that 
-exits instantly (``true`` is pretty much the smallest, simplest program 
-that you can run). Once created you can mount its volumes in any other 
-container using the ``-volumes-from`` option; irrespecive of whether the
-container is running or not. 
+For a Dockerfile, the VOLUME instruction will add one or more new
+volumes to any container created from the image::
 
-Or, you can use the VOLUME instruction in a Dockerfile to add one or more new
-volumes to any container created from that image::
+  VOLUME ["/var/volume1", "/var/volume2"]
 
-  # BUILD-USING:        docker build -t data .
-  # RUN-USING:          docker run -name DATA data 
-  FROM          busybox
-  VOLUME        ["/var/volume1", "/var/volume2"]
-  CMD           ["/usr/bin/true"]
 
-Creating and mounting a Data Volume Container
----------------------------------------------
+Mount Volumes from an Existing Container:
+-----------------------------------------
 
-If you have some persistent data that you want to share between containers, 
-or want to use from non-persistent containers, its best to create a named
-Data Volume Container, and then to mount the data from it.
+The command below creates a new container which is runnning as daemon
+``-d`` and with one volume ``/var/lib/couchdb``::
 
-Create a named container with volumes to share (``/var/volume1`` and ``/var/volume2``)::
+  COUCH1=$(sudo docker run -d -v /var/lib/couchdb shykes/couchdb:2013-05-03)
 
-  $ docker run -v /var/volume1 -v /var/volume2 -name DATA busybox true
+From the container id of that previous container ``$COUCH1`` it's
+possible to create new container sharing the same volume using the
+parameter ``-volumes-from container_id``::
 
-Then mount those data volumes into your application containers::
+  COUCH2=$(sudo docker run -d -volumes-from $COUCH1 shykes/couchdb:2013-05-03)
 
-  $ docker run -t -i -rm -volumes-from DATA -name client1 ubuntu bash
+Now, the second container has the all the information from the first volume.
 
-You can use multiple ``-volumes-from`` parameters to bring together multiple 
-data volumes from multiple containers. 
-
-Interestingly, you can mount the volumes that came from the ``DATA`` container in 
-yet another container via the ``client1`` middleman container::
-
-  $ docker run -t -i -rm -volumes-from client1 ubuntu -name client2 bash
-
-This allows you to abstract the actual data source from users of that data, 
-similar to :ref:`ambassador_pattern_linking <ambassador_pattern_linking>`.
-
-If you remove containers that mount volumes, including the initial DATA container, 
-or the middleman, the volumes will not be deleted until there are no containers still
-referencing those volumes. This allows you to upgrade, or effectivly migrate data volumes
-between containers.
 
 Mount a Host Directory as a Container Volume:
 ---------------------------------------------
@@ -91,13 +68,13 @@ Mount a Host Directory as a Container Volume:
   -v=[]: Create a bind mount with: [host-dir]:[container-dir]:[rw|ro].
   If "host-dir" is missing, then docker creates a new volume.
 
-This is not available from a Dockerfile as it makes the built image less portable
-or shareable. [host-dir] volumes are 100% host dependent and will break on any 
-other machine.
+This is not available for a Dockerfile due the portability and sharing
+purpose of it. The [host-dir] volumes is something 100% host dependent
+and will break on any other machine.
 
 For example::
 
-  sudo docker run -v /var/logs:/var/host_logs:ro ubuntu bash
+  sudo docker run -v /var/logs:/var/host_logs:ro shykes/couchdb:2013-05-03
 
 The command above mounts the host directory ``/var/logs`` into the
 container with read only permissions as ``/var/host_logs``.
@@ -110,6 +87,3 @@ Known Issues
 * :issue:`2702`: "lxc-start: Permission denied - failed to mount"
   could indicate a permissions problem with AppArmor. Please see the
   issue for a workaround.
-* :issue:`2528`:  the busybox container is used to make the resulting container as small and
-  simple as possible - whenever you need to interact with the data in the volume
-  you mount it into another container.

docs/sources/use/workingwithrepository.rst

@@ -1,11 +1,11 @@
-:title: Share Images via Repositories
+:title: Working With Repositories
 :description: Repositories allow users to share images.
 :keywords: repo, repositories, usage, pull image, push image, image, documentation
 
 .. _working_with_the_repository:
 
-Share Images via Repositories
-=============================
+Working with Repositories
+=========================
 
 A *repository* is a hosted collection of tagged :ref:`images
 <image_def>` that together create the file system for a container. The
@@ -152,41 +152,6 @@ or tag.
 
 .. _using_private_repositories:
 
-Trusted Builds
---------------
-
-Trusted Builds automate the building and updating of images from GitHub, directly 
-on docker.io servers. It works by adding a commit hook to your selected repository,
-triggering a build and update when you push a commit.
-
-To setup a trusted build
-++++++++++++++++++++++++
-
-#. Create a `Docker Index account <https://index.docker.io/>`_ and login.
-#. Link your GitHub account through the ``Link Accounts`` menu.
-#. `Configure a Trusted build <https://index.docker.io/builds/>`_.
-#. Pick a GitHub project that has a ``Dockerfile`` that you want to build.
-#. Pick the branch you want to build (the default is the  ``master`` branch).
-#. Give the Trusted Build a name.
-#. Assign an optional Docker tag to the Build.
-#. Specify where the ``Dockerfile`` is located. The default is ``/``.
-
-Once the Trusted Build is configured it will automatically trigger a build, and
-in a few minutes, if there are no errors, you will see your new trusted build
-on the Docker Index. It will will stay in sync with your GitHub repo until you
-deactivate the Trusted Build.
-
-If you want to see the status of your Trusted Builds you can go to your
-`Trusted Builds page <https://index.docker.io/builds/>`_ on the Docker index,
-and it will show you the status of your builds, and the build history.
-
-Once you've created a Trusted Build you can deactive or delete it. You cannot
-however push to a Trusted Build with the ``docker push`` command. You can only
-manage it by committing code to your GitHub repository.
-
-You can create multiple Trusted Builds per repository and configure them to
-point to specific ``Dockerfile``'s or Git branches.
-
 Private Repositories
 --------------------
 

docs/theme/docker/layout.html

@@ -35,7 +35,7 @@
     %}
 
     {#
-        This part is hopefully complex because things like |cut '/index/' are not available in Sphinx jinja
+        This part is hopefully complex because things like |cut '/index/' are not available in spinx jinja
         and will make it crash. (and we need index/ out.
     #}
     <link rel="canonical" href="http://docs.docker.io/en/latest/
@@ -86,26 +86,26 @@
     </div>
 </div>
 
-<div class="container-fluid">
+<div class="container">
 
     <!-- Docs nav
      ================================================== -->
-    <div class="row-fluid main-row">
+    <div class="row main-row">
 
-        <div class="sidebar bs-docs-sidebar">
+        <div class="span3 sidebar bs-docs-sidebar">
             <div class="page-title" >
                 <h4>DOCUMENTATION</h4>
             </div>
             
             {{ toctree(collapse=False, maxdepth=3) }}
 	    <form>
-	      <input type="text" id="st-search-input" class="st-search-input span3" placeholder="search in documentation" style="width:210px;" />
+	      <input type="text" id="st-search-input" class="st-search-input span3" style="width:160px;" />
           <div id="st-results-container"></div>
 	    </form>
         </div>
 
         <!-- body block -->
-        <div class="main-content">
+        <div class="span9 main-content">
 
             <!-- Main section
             ================================================== -->
@@ -134,22 +134,13 @@
                         </div>
 
                         <div class="social links">
-                            <a title="Docker on Twitter" class="twitter" href="http://twitter.com/docker">Twitter</a>
-                            <a title="Docker on GitHub" class="github" href="https://github.com/dotcloud/docker/">GitHub</a>
-                            <a title="Docker on Reddit" class="reddit" href="http://www.reddit.com/r/Docker/">Reddit</a>
-                            <a title="Docker on Google+" class="googleplus" href="https://plus.google.com/u/0/b/100381662757235514581/communities/108146856671494713993">Google+</a>
-                            <a title="Docker on Facebook" class="facebook" href="https://www.facebook.com/docker.run">Facebook</a>
-                            <a title="Docker on SlideShare" class="slideshare" href="http://www.slideshare.net/dotCloud">Slideshare</a>
-                            <a title="Docker on Youtube" class="youtube" href="http://www.youtube.com/user/dockerrun/">Youtube</a>
-                            <a title="Docker on Flickr" class="flickr" href="http://www.flickr.com/photos/99741659@N08/">Flickr</a>
-                            <a title="Docker on LinkedIn" class="linkedin" href="http://www.linkedin.com/company/dotcloud">LinkedIn</a>
+                            <a class="twitter" href="http://twitter.com/docker">Twitter</a>
+                            <a class="github" href="https://github.com/dotcloud/docker/">GitHub</a>
                         </div>
 
                         <div class="tbox version-flyer ">
                             <div class="content">
-                                <p class="version-note">Note: You are currently browsing the development documentation. The current release may work differently.</p>
-
-                                <small>Available versions:</small>
+                                <small>Current version:</small>
                                 <ul class="inline">
                                     {% for slug, url in versions %}
                                     <li class="alternative"><a href="{{ url }}{%- for word in pagename.split('/') -%}
@@ -172,7 +163,6 @@
         </div>
         <!-- end of footer -->
     </div>
-
 </div>
 
 

docs/theme/docker/static/css/main.css

@@ -62,12 +62,9 @@ p a.btn {
   -moz-box-shadow: 0 1px 4px rgba(0, 0, 0, 0.065);
   box-shadow: 0 1px 4px rgba(0, 0, 0, 0.065);
 }
-.brand-logo a {
+.brand.logo a {
   color: white;
 }
-.brand-logo a img {
-  width: auto;
-}
 .inline-icon {
   margin-bottom: 6px;
 }
@@ -189,15 +186,8 @@ body {
 .main-row {
   margin-top: 40px;
 }
-.sidebar {
-  width: 215px;
-  float: left;
-}
 .main-content {
   padding: 16px 18px inherit;
-  margin-left: 230px;
-  /* space for sidebar */
-
 }
 /* =======================
    Social footer
@@ -208,54 +198,20 @@ body {
 }
 .social .twitter,
 .social .github,
-.social .googleplus,
-.social .facebook,
-.social .slideshare,
-.social .linkedin,
-.social .flickr,
-.social .youtube,
-.social .reddit {
-  background: url("../img/social/docker_social_logos.png") no-repeat transparent;
+.social .googleplus {
+  background: url("https://www.docker.io/static/img/footer-links.png") no-repeat transparent;
   display: inline-block;
-  height: 32px;
+  height: 35px;
   overflow: hidden;
   text-indent: 9999px;
-  width: 32px;
-  margin-right: 5px;
-}
-.social :hover {
-  -webkit-transform: rotate(-10deg);
-  -moz-transform: rotate(-10deg);
-  -o-transform: rotate(-10deg);
-  -ms-transform: rotate(-10deg);
-  transform: rotate(-10deg);
+  width: 35px;
+  margin-right: 10px;
 }
 .social .twitter {
-  background-position: -160px 0px;
-}
-.social .reddit {
-  background-position: -256px 0px;
+  background-position: 0px 2px;
 }
 .social .github {
-  background-position: -64px 0px;
-}
-.social .googleplus {
-  background-position: -96px 0px;
-}
-.social .facebook {
-  background-position: 0px 0px;
-}
-.social .slideshare {
-  background-position: -128px 0px;
-}
-.social .youtube {
-  background-position: -192px 0px;
-}
-.social .flickr {
-  background-position: -32px 0px;
-}
-.social .linkedin {
-  background-position: -224px 0px;
+  background-position: -59px 2px;
 }
 form table th {
   vertical-align: top;
@@ -386,7 +342,6 @@ div.alert.alert-block {
   border: 1px solid #88BABC;
   padding: 5px;
   font-size: larger;
-  max-width: 300px;
 }
 .version-flyer .content {
   padding-right: 45px;
@@ -396,18 +351,18 @@ div.alert.alert-block {
   background-position: right center;
   background-repeat: no-repeat;
 }
+.version-flyer .alternative {
+  visibility: hidden;
+  display: none;
+}
 .version-flyer .active-slug {
   visibility: visible;
   display: inline-block;
-  font-weight: bolder;
 }
 .version-flyer:hover .alternative {
   animation-duration: 1s;
   display: inline-block;
-}
-.version-flyer .version-note {
-  font-size: 16px;
-  color: black;
+  visibility: visible;
 }
 /* =====================================
   Styles for 
@@ -455,20 +410,3 @@ dt:hover > a.headerlink {
 .admonition.seealso {
   border-color: #23cb1f;
 }
-/* Add styles for other types of comments */
-.versionchanged,
-.versionadded,
-.versionmodified,
-.deprecated {
-  font-size: larger;
-  font-weight: bold;
-}
-.versionchanged {
-  color: lightseagreen;
-}
-.versionadded {
-  color: mediumblue;
-}
-.deprecated {
-  color: orangered;
-}

docs/theme/docker/static/css/main.less

@@ -98,6 +98,7 @@ p a {
 }
 
 
+
 .navbar .brand {
 	margin-left: 0px;
 	float: left;
@@ -125,11 +126,9 @@ p a {
   box-shadow: 0 1px 4px rgba(0, 0, 0, 0.065);
 }
 
-.brand-logo a {
+.brand.logo a {
 	color: white;
-  img {
-    width: auto;
-  }
+
 }
 
 .logo {
@@ -318,18 +317,10 @@ body {
   margin-top: 40px;
 }
 
-.sidebar {
-  width: 215px;
-  float: left;
-}
-
 .main-content {
   padding: 16px 18px inherit;
-  margin-left: 230px; /* space for sidebar */
 }
 
-
-
 /* =======================
    Social footer
 ======================= */
@@ -339,64 +330,24 @@ body {
   margin-top: 15px;
 }
 
-.social {
-  .twitter, .github, .googleplus, .facebook, .slideshare, .linkedin, .flickr, .youtube, .reddit {
-    background: url("../img/social/docker_social_logos.png") no-repeat transparent;
-    display: inline-block;
-    height: 32px;
-    overflow: hidden;
-    text-indent: 9999px;
-    width: 32px;
-    margin-right: 5px;
-  }
-}
-
-.social :hover {
-  -webkit-transform: rotate(-10deg);
-     -moz-transform: rotate(-10deg);
-       -o-transform: rotate(-10deg);
-      -ms-transform: rotate(-10deg);
-          transform: rotate(-10deg);
+.social .twitter, .social .github, .social .googleplus {
+  background: url("https://www.docker.io/static/img/footer-links.png") no-repeat transparent;
+  display: inline-block;
+  height: 35px;
+  overflow: hidden;
+  text-indent: 9999px;
+  width: 35px;
+  margin-right: 10px;
 }
 
 .social .twitter {
-  background-position: -160px 0px;
-}
-
-.social .reddit {
-  background-position: -256px 0px;
+  background-position: 0px 2px;
 }
 
 .social .github {
-  background-position: -64px 0px;
+  background-position: -59px 2px;
 }
 
-.social .googleplus {
-  background-position: -96px 0px;
-}
-
-.social .facebook {
-  background-position: -0px 0px;
-}
-
-.social .slideshare {
-  background-position: -128px 0px;
-}
-
-.social .youtube {
-  background-position: -192px 0px;
-}
-
-.social .flickr {
-  background-position: -32px 0px;
-}
-
-.social .linkedin {
-  background-position: -224px 0px;
-}
-
-
-
 // Styles on the forms
 // ----------------------------------
 
@@ -577,34 +528,31 @@ div.alert.alert-block {
   border: 1px solid #88BABC;
   padding: 5px;
   font-size: larger;
-  max-width: 300px;
 
   .content {
     padding-right: 45px;
     margin-top: 7px;
     margin-left: 7px;
+    // display: inline-block;
     background-image: url('../img/container3.png');
     background-position: right center; 
     background-repeat: no-repeat;
   }
 
   .alternative {
+    visibility: hidden;
+    display: none;
   }
 
   .active-slug {
     visibility: visible;
     display: inline-block;
-    font-weight: bolder;
   }
 
   &:hover .alternative {
     animation-duration: 1s;
     display: inline-block;
-  }
-
-  .version-note {
-    font-size: 16px;
-    color: black;
+    visibility: visible;
   }
 
 }
@@ -664,24 +612,3 @@ dt:hover > a.headerlink {
 
 }
 
-/* Add styles for other types of comments */
-
-.versionchanged,
-.versionadded,
-.versionmodified,
-.deprecated {
-   font-size: larger;
-   font-weight: bold;
-}
-
-.versionchanged {
-  color: lightseagreen;
-}
-
-.versionadded {
-   color: mediumblue;
-}
-
-.deprecated {
-   color: orangered;
-}

docs/theme/docker/static/js/docs.js

@@ -53,6 +53,14 @@ $(function(){
         }
     }
 
+    if (doc_version == "") {
+        $('.version-flyer ul').html('<li class="alternative active-slug"><a href="" title="Switch to local">Local</a></li>');
+    }
+
+    // mark the active documentation in the version widget
+    $(".version-flyer a:contains('" + doc_version + "')").parent().addClass('active-slug');
+
+
     // attached handler on click
     // Do not attach to first element or last (intro, faq) so that
     // first and last link directly instead of accordian
@@ -87,18 +95,4 @@ $(function(){
     // add class to all those which have children
     $('.sidebar > ul > li').not(':last').not(':first').addClass('has-children');
 
-
-    if (doc_version == "") {
-        $('.version-flyer ul').html('<li class="alternative active-slug"><a href="" title="Switch to local">Local</a></li>');
-    }
-
-    if (doc_version == "master") {
-        $('.version-flyer .version-note').hide();
-    }
-
-    // mark the active documentation in the version widget
-    $(".version-flyer a:contains('" + doc_version + "')").parent().addClass('active-slug').setAttribute("title", "Current version");
-
-
-
 });

engine/MAINTAINERS

@@ -1 +1 @@
-#Solomon Hykes <solomon@dotcloud.com> Temporarily unavailable
+Solomon Hykes <solomon@dotcloud.com>

engine/engine.go

@@ -3,15 +3,13 @@ package engine
 import (
 	"fmt"
 	"github.com/dotcloud/docker/utils"
-	"io"
 	"log"
 	"os"
-	"path/filepath"
 	"runtime"
 	"strings"
 )
 
-type Handler func(*Job) Status
+type Handler func(*Job) string
 
 var globalHandlers map[string]Handler
 
@@ -36,9 +34,6 @@ type Engine struct {
 	handlers map[string]Handler
 	hack     Hack // data for temporary hackery (see hack.go)
 	id       string
-	Stdout   io.Writer
-	Stderr   io.Writer
-	Stdin    io.Reader
 }
 
 func (eng *Engine) Root() string {
@@ -75,36 +70,16 @@ func New(root string) (*Engine, error) {
 		log.Printf("WARNING: %s\n", err)
 	} else {
 		if utils.CompareKernelVersion(k, &utils.KernelVersionInfo{Kernel: 3, Major: 8, Minor: 0}) < 0 {
-			if os.Getenv("DOCKER_NOWARN_KERNEL_VERSION") == "" {
-				log.Printf("WARNING: You are running linux kernel version %s, which might be unstable running docker. Please upgrade your kernel to 3.8.0.", k.String())
-			}
+			log.Printf("WARNING: You are running linux kernel version %s, which might be unstable running docker. Please upgrade your kernel to 3.8.0.", k.String())
 		}
 	}
-
 	if err := os.MkdirAll(root, 0700); err != nil && !os.IsExist(err) {
 		return nil, err
 	}
-
-	// Docker makes some assumptions about the "absoluteness" of root
-	// ... so let's make sure it has no symlinks
-	if p, err := filepath.Abs(root); err != nil {
-		log.Fatalf("Unable to get absolute root (%s): %s", root, err)
-	} else {
-		root = p
-	}
-	if p, err := filepath.EvalSymlinks(root); err != nil {
-		log.Fatalf("Unable to canonicalize root (%s): %s", root, err)
-	} else {
-		root = p
-	}
-
 	eng := &Engine{
 		root:     root,
 		handlers: make(map[string]Handler),
 		id:       utils.RandomString(),
-		Stdout:   os.Stdout,
-		Stderr:   os.Stderr,
-		Stdin:    os.Stdin,
 	}
 	// Copy existing global handlers
 	for k, v := range globalHandlers {
@@ -124,12 +99,10 @@ func (eng *Engine) Job(name string, args ...string) *Job {
 		Eng:    eng,
 		Name:   name,
 		Args:   args,
-		Stdin:  NewInput(),
-		Stdout: NewOutput(),
-		Stderr: NewOutput(),
-		env:    &Env{},
+		Stdin:  os.Stdin,
+		Stdout: os.Stdout,
+		Stderr: os.Stderr,
 	}
-	job.Stderr.Add(utils.NopWriteCloser(eng.Stderr))
 	handler, exists := eng.handlers[name]
 	if exists {
 		job.handler = handler
@@ -139,5 +112,5 @@ func (eng *Engine) Job(name string, args ...string) *Job {
 
 func (eng *Engine) Logf(format string, args ...interface{}) (n int, err error) {
 	prefixedFormat := fmt.Sprintf("[%s] %s\n", eng, strings.TrimRight(format, "\n"))
-	return fmt.Fprintf(eng.Stderr, prefixedFormat, args...)
+	return fmt.Fprintf(os.Stderr, prefixedFormat, args...)
 }

engine/engine_test.go

@@ -1,9 +1,6 @@
 package engine
 
 import (
-	"io/ioutil"
-	"os"
-	"path"
 	"testing"
 )
 
@@ -18,7 +15,7 @@ func TestRegister(t *testing.T) {
 
 	eng := newTestEngine(t)
 
-	//Should fail because global handlers are copied
+	//Should fail because globan handlers are copied
 	//at the engine creation
 	if err := eng.Register("dummy1", nil); err == nil {
 		t.Fatalf("Expecting error, got none")
@@ -41,9 +38,8 @@ func TestJob(t *testing.T) {
 		t.Fatalf("job1.handler should be empty")
 	}
 
-	h := func(j *Job) Status {
-		j.Printf("%s\n", j.Name)
-		return 42
+	h := func(j *Job) string {
+		return j.Name
 	}
 
 	eng.Register("dummy2", h)
@@ -53,51 +49,7 @@ func TestJob(t *testing.T) {
 		t.Fatalf("job2.handler shouldn't be nil")
 	}
 
-	if job2.handler(job2) != 42 {
+	if job2.handler(job2) != job2.Name {
 		t.Fatalf("handler dummy2 was not found in job2")
 	}
 }
-
-func TestEngineRoot(t *testing.T) {
-	tmp, err := ioutil.TempDir("", "docker-test-TestEngineCreateDir")
-	if err != nil {
-		t.Fatal(err)
-	}
-	defer os.RemoveAll(tmp)
-	dir := path.Join(tmp, "dir")
-	eng, err := New(dir)
-	if err != nil {
-		t.Fatal(err)
-	}
-	if st, err := os.Stat(dir); err != nil {
-		t.Fatal(err)
-	} else if !st.IsDir() {
-		t.Fatalf("engine.New() created something other than a directory at %s", dir)
-	}
-	if r := eng.Root(); r != dir {
-		t.Fatalf("Expected: %v\nReceived: %v", dir, r)
-	}
-}
-
-func TestEngineString(t *testing.T) {
-	eng1 := newTestEngine(t)
-	defer os.RemoveAll(eng1.Root())
-	eng2 := newTestEngine(t)
-	defer os.RemoveAll(eng2.Root())
-	s1 := eng1.String()
-	s2 := eng2.String()
-	if eng1 == eng2 {
-		t.Fatalf("Different engines should have different names (%v == %v)", s1, s2)
-	}
-}
-
-func TestEngineLogf(t *testing.T) {
-	eng := newTestEngine(t)
-	defer os.RemoveAll(eng.Root())
-	input := "Test log line"
-	if n, err := eng.Logf("%s\n", input); err != nil {
-		t.Fatal(err)
-	} else if n < len(input) {
-		t.Fatalf("Test: Logf() should print at least as much as the input\ninput=%d\nprinted=%d", len(input), n)
-	}
-}

engine/env.go

@@ -1,234 +0,0 @@
-package engine
-
-import (
-	"bytes"
-	"encoding/json"
-	"fmt"
-	"io"
-	"strconv"
-	"strings"
-)
-
-type Env []string
-
-func (env *Env) Get(key string) (value string) {
-	// FIXME: use Map()
-	for _, kv := range *env {
-		if strings.Index(kv, "=") == -1 {
-			continue
-		}
-		parts := strings.SplitN(kv, "=", 2)
-		if parts[0] != key {
-			continue
-		}
-		if len(parts) < 2 {
-			value = ""
-		} else {
-			value = parts[1]
-		}
-	}
-	return
-}
-
-func (env *Env) Exists(key string) bool {
-	_, exists := env.Map()[key]
-	return exists
-}
-
-func (env *Env) GetBool(key string) (value bool) {
-	s := strings.ToLower(strings.Trim(env.Get(key), " \t"))
-	if s == "" || s == "0" || s == "no" || s == "false" || s == "none" {
-		return false
-	}
-	return true
-}
-
-func (env *Env) SetBool(key string, value bool) {
-	if value {
-		env.Set(key, "1")
-	} else {
-		env.Set(key, "0")
-	}
-}
-
-func (env *Env) GetInt(key string) int {
-	return int(env.GetInt64(key))
-}
-
-func (env *Env) GetInt64(key string) int64 {
-	s := strings.Trim(env.Get(key), " \t")
-	val, err := strconv.ParseInt(s, 10, 64)
-	if err != nil {
-		return -1
-	}
-	return val
-}
-
-func (env *Env) SetInt(key string, value int) {
-	env.Set(key, fmt.Sprintf("%d", value))
-}
-
-func (env *Env) SetInt64(key string, value int64) {
-	env.Set(key, fmt.Sprintf("%d", value))
-}
-
-// Returns nil if key not found
-func (env *Env) GetList(key string) []string {
-	sval := env.Get(key)
-	if sval == "" {
-		return nil
-	}
-	l := make([]string, 0, 1)
-	if err := json.Unmarshal([]byte(sval), &l); err != nil {
-		l = append(l, sval)
-	}
-	return l
-}
-
-func (env *Env) GetJson(key string, iface interface{}) error {
-	sval := env.Get(key)
-	if sval == "" {
-		return nil
-	}
-	return json.Unmarshal([]byte(sval), iface)
-}
-
-func (env *Env) SetJson(key string, value interface{}) error {
-	sval, err := json.Marshal(value)
-	if err != nil {
-		return err
-	}
-	env.Set(key, string(sval))
-	return nil
-}
-
-func (env *Env) SetList(key string, value []string) error {
-	return env.SetJson(key, value)
-}
-
-func (env *Env) Set(key, value string) {
-	*env = append(*env, key+"="+value)
-}
-
-func NewDecoder(src io.Reader) *Decoder {
-	return &Decoder{
-		json.NewDecoder(src),
-	}
-}
-
-type Decoder struct {
-	*json.Decoder
-}
-
-func (decoder *Decoder) Decode() (*Env, error) {
-	m := make(map[string]interface{})
-	if err := decoder.Decoder.Decode(&m); err != nil {
-		return nil, err
-	}
-	env := &Env{}
-	for key, value := range m {
-		env.SetAuto(key, value)
-	}
-	return env, nil
-}
-
-// DecodeEnv decodes `src` as a json dictionary, and adds
-// each decoded key-value pair to the environment.
-//
-// If `src` cannot be decoded as a json dictionary, an error
-// is returned.
-func (env *Env) Decode(src io.Reader) error {
-	m := make(map[string]interface{})
-	if err := json.NewDecoder(src).Decode(&m); err != nil {
-		return err
-	}
-	for k, v := range m {
-		env.SetAuto(k, v)
-	}
-	return nil
-}
-
-func (env *Env) SetAuto(k string, v interface{}) {
-	// FIXME: we fix-convert float values to int, because
-	// encoding/json decodes integers to float64, but cannot encode them back.
-	// (See http://golang.org/src/pkg/encoding/json/decode.go#L46)
-	if fval, ok := v.(float64); ok {
-		env.SetInt64(k, int64(fval))
-	} else if sval, ok := v.(string); ok {
-		env.Set(k, sval)
-	} else if val, err := json.Marshal(v); err == nil {
-		env.Set(k, string(val))
-	} else {
-		env.Set(k, fmt.Sprintf("%v", v))
-	}
-}
-
-func (env *Env) Encode(dst io.Writer) error {
-	m := make(map[string]interface{})
-	for k, v := range env.Map() {
-		var val interface{}
-		if err := json.Unmarshal([]byte(v), &val); err == nil {
-			// FIXME: we fix-convert float values to int, because
-			// encoding/json decodes integers to float64, but cannot encode them back.
-			// (See http://golang.org/src/pkg/encoding/json/decode.go#L46)
-			if fval, isFloat := val.(float64); isFloat {
-				val = int(fval)
-			}
-			m[k] = val
-		} else {
-			m[k] = v
-		}
-	}
-	if err := json.NewEncoder(dst).Encode(&m); err != nil {
-		return err
-	}
-	return nil
-}
-
-func (env *Env) WriteTo(dst io.Writer) (n int64, err error) {
-	// FIXME: return the number of bytes written to respect io.WriterTo
-	return 0, env.Encode(dst)
-}
-
-func (env *Env) Export(dst interface{}) (err error) {
-	defer func() {
-		if err != nil {
-			err = fmt.Errorf("ExportEnv %s", err)
-		}
-	}()
-	var buf bytes.Buffer
-	// step 1: encode/marshal the env to an intermediary json representation
-	if err := env.Encode(&buf); err != nil {
-		return err
-	}
-	// step 2: decode/unmarshal the intermediary json into the destination object
-	if err := json.NewDecoder(&buf).Decode(dst); err != nil {
-		return err
-	}
-	return nil
-}
-
-func (env *Env) Import(src interface{}) (err error) {
-	defer func() {
-		if err != nil {
-			err = fmt.Errorf("ImportEnv: %s", err)
-		}
-	}()
-	var buf bytes.Buffer
-	if err := json.NewEncoder(&buf).Encode(src); err != nil {
-		return err
-	}
-	if err := env.Decode(&buf); err != nil {
-		return err
-	}
-	return nil
-}
-
-func (env *Env) Map() map[string]string {
-	m := make(map[string]string)
-	for _, kv := range *env {
-		parts := strings.SplitN(kv, "=", 2)
-		m[parts[0]] = parts[1]
-	}
-	return m
-}

engine/env_test.go

@@ -37,16 +37,16 @@ func TestSetenvBool(t *testing.T) {
 	job := mkJob(t, "dummy")
 	job.SetenvBool("foo", true)
 	if val := job.GetenvBool("foo"); !val {
-		t.Fatalf("GetenvBool returns incorrect value: %t", val)
+		t.Fatalf("GetenvBool returns incorrect value: %b", val)
 	}
 
 	job.SetenvBool("bar", false)
 	if val := job.GetenvBool("bar"); val {
-		t.Fatalf("GetenvBool returns incorrect value: %t", val)
+		t.Fatalf("GetenvBool returns incorrect value: %b", val)
 	}
 
 	if val := job.GetenvBool("nonexistent"); val {
-		t.Fatalf("GetenvBool returns incorrect value: %t", val)
+		t.Fatalf("GetenvBool returns incorrect value: %b", val)
 	}
 }