--netflag to allow advanced network configuration such as host networking so that containers can use the host's network interfaces
docker psto the documentation.
docker restartto the documentation.
docker imagesto the docs.
--lxc-confis lxc only.
docker run -adoes in the docs.
docker infoeven when not in debug mode.
docker images --treeand
docker images --viz.
docker commit -run.
docker infoeven when not in debug mode.
--rmthe default for
127.0.0.1:4243and remove the default port for tcp.
docker commit. This makes
docker commit --runwork again.
docker run -it).
docker run -i -t(issue #3336).
docker rmto force removal of running containers.
DOCKER_RAMDISKenvironment variable to make Docker work when the root is on a ramdisk.
docker build --rm. This adds a missing error check to ensure failures to remove containers are detected and reported
docker commit. This makes docker commit store
--runin the image configuration
docker cpstream is closed properly
Images and containers can be removed much faster
Building an image from source with docker build is now much faster
The Docker daemon starts and stops much faster
The memory footprint of many common operations has been reduced, by streaming files instead of buffering them in memory, fixing memory leaks, and fixing various suboptimal memory allocations
Several race conditions were fixed, making Docker more stable under very high concurrency load. This makes Docker more stable and less likely to crash and reduces the memory footprint of many common operations
All packaging operations are now built on the Go language’s standard tar implementation, which is bundled with Docker itself. This makes packaging more portable across host distributions, and solves several issues caused by quirks and incompatibilities between different distributions of tar
Docker can now create, remove and modify larger numbers of containers and images graciously thanks to more aggressive releasing of system resources. For example the storage driver API now allows Docker to do reference counting on mounts created by the drivers With the ongoing changes to the networking and execution subsystems of docker testing these areas have been a focus of the refactoring. By moving these subsystems into separate packages we can test, analyze, and monitor coverage and quality of these packages
Many components have been separated into smaller sub-packages, each with a dedicated test suite. As a result the code is better-tested, more readable and easier to change
The ADD instruction now supports caching, which avoids unnecessarily re-uploading the same source content again and again when it hasn’t changed
The new ONBUILD instruction adds to your image a “trigger” instruction to be executed at a later time, when the image is used as the base for another build
Docker now ships with an experimental storage driver which uses the BTRFS filesystem for copy-on-write
Docker is officially supported on Mac OSX
The Docker daemon supports systemd socket activation
-mtuflag in several GCE zones
lxc-checkconfigas a way to check for some of the necessary kernel configuration
-ato our Go build flags, removing the need for recompiling the stdlib manually
docker pullprogress bar display issues
docker topin pure Go to work more consistently, and even inside Docker-in-Docker (thus removing the shell injection vulnerability present in some versions of
-H unix://to work similarly to
-H tcp://by inserting the default values for missing portions
-gto work as expected
docker images -tree
-Soption to external tar invocation for more efficient spare file handling
-mtuoption to Docker daemon for configuring MTU
docker buildto exit with a non-zero exit code on error
DOCKER_HOSTenvironment variable to configure the client
-Hflag without specifying it manually for every invocation
docker log -fto stream logs
docker buildnow returns the correct exit code
docker portto display correct port
docker buildnow check that the dockerfile exists client side
docker attachnow returns the correct exit code
docker rmwith volumes
apt-get install curlto Ubuntu docs
vagrant upis actually doing
docker startset error code upon error
docker runset the same error code as the process started
docker run -nand
docker -d -b=none
t ignore last line in Dockerfile when it doesnt end with \n
Initial public release