Docker Machine Docker Machine overview Install Docker Machine Install a machine on your local system using VirtualBox Install multiple machines on your cloud provider Digital Ocean Example AWS Example Machine concepts and help Migrate from Boot2Docker to Docker Machine Docker Machine driver reference Docker Machine subcommand reference

push Usage: docker push [OPTIONS] NAME[:TAG] Push an image or a repository to the registry --disable-content-trust=true Skip image signing --help Print usage Use docker push to share your images to the Docker Hub registry or to a self-hosted one. Killing the docker push process, for example by pressing CTRL-c while it is running in a terminal, will terminate the push operation. Registry credentials are managed by docker login.

volume inspect Usage: docker volume inspect [OPTIONS] VOLUME [VOLUME...] Return low-level information on a volume -f, --format= Format the output using the given go template. --help Print usage Returns information about a volume. By default, this command renders all results in a JSON array. You can specify an alternate format to execute a given template for each result. Go’s text/template package describes all the details of the format. Example output: $ docker volume

Configure container DNS The information in this section explains configuring container DNS within the Docker default bridge. This is a bridge network named bridge created automatically when you install Docker. Note: The Docker networks feature allows you to create user-defined networks in addition to the default bridge network. Please refer to the Docker Embedded DNS section for more information on DNS configurations in user-defined networks. How can Docker supply each container with a hostna

run Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...] Run a command in a new container -a, --attach=[] Attach to STDIN, STDOUT or STDERR --add-host=[] Add a custom host-to-IP mapping (host:ip) --blkio-weight=0 Block IO weight (relative weight) --blkio-weight-device=[] Block IO weight (relative device weight, format: `DEVICE_NAME:WEIGHT`) --cpu-shares=0 CPU shares (relative weight) --cap-add=[] Add L

Swarm and container networks Docker Swarm is fully compatible with Docker’s networking features. This includes the multi-host networking feature which allows creation of custom container networks that span multiple Docker hosts. Before using Swarm with a custom network, read through the conceptual information in Docker container networking. You should also have walked through the Get started with multi-host networking example. Create a custom network in a Swarm cluster Multi-host networks requi

pull Usage: pull [options] [SERVICE...] Options: --ignore-pull-failures Pull what it can and ignores images with pull failures. Pulls service images.

manage — Create a Swarm manager Prerequisite: Before using manage to create a Swarm manager, establish a discovery backend as described in this discovery topic. The manage command creates a Swarm manager whose purpose is to receive commands on behalf of the cluster and assign containers to Swarm nodes. You can create multiple Swarm managers as part of a high-availability cluster. To create a Swarm manager, use the following syntax: $ docker run swarm manage [OPTIONS] <discovery> For exam

Getting Started On this page you build a simple Python web application running on Docker Compose. The application uses the Flask framework and increments a value in Redis. While the sample uses Python, the concepts demonstrated here should be understandable even if you’re not familiar with it. Prerequisites Make sure you have already installed both Docker Engine and Docker Compose. You don’t need to install Python, it is provided by a Docker image. Step 1: Setup Create a directory for the proj

Understand container communication The information in this section explains container communication within the Docker default bridge. This is a bridge network named bridge created automatically when you install Docker. Note: The Docker networks feature allows you to create user-defined networks in addition to the default bridge network. Communicating to the outside world Whether a container can talk to the world is governed by two factors. The first factor is whether the host machine is forward