help - Display information about a command The help command displays information about how to use a command. For example, to see a list of Swarm options and commands, enter: $ docker run swarm --help To see a list of arguments and options for a specific Swarm command, enter: $ docker run swarm <command> --help For example: $ docker run swarm list --help Usage: swarm list [OPTIONS] <discovery> List nodes in a cluster Arguments: <discovery> discovery service to use [$S

load Usage: docker load [OPTIONS] Load an image from a tar archive or STDIN --help Print usage -i, --input="" Read from a tar archive file, instead of STDIN. The tarball may be compressed with gzip, bzip, or xz -q, --quiet Suppress the load output. Without this option, a progress bar is displayed. Loads a tarred repository from a file or the standard input stream. Restores both images and tags. $ docker images REPOSITORY TAG IMAGE ID

kill Usage: docker-machine kill [arg...] Kill (abruptly force stop) a machine Description: Argument(s) are one or more machine names. For example: $ docker-machine ls NAME ACTIVE DRIVER STATE URL dev * virtualbox Running tcp://192.168.99.104:2376 $ docker-machine kill dev $ docker-machine ls NAME ACTIVE DRIVER STATE URL dev * virtualbox Stopped

Docker Remote API Docker’s Remote API uses an open schema model. In this model, unknown properties in incoming messages are ignored. Client applications need to take this behavior into account to ensure they do not break when talking to newer Docker daemons. The API tends to be REST, but for some complex commands, like attach or pull, the HTTP connection is hijacked to transport STDOUT, STDIN, and STDERR. By default the Docker daemon listens on unix:///var/run/docker.sock and the client must ha

volume create Usage: docker volume create [OPTIONS] Create a volume -d, --driver=local Specify volume driver name --help Print usage --label=[] Set metadata for a volume --name= Specify volume name -o, --opt=map[] Set driver specific options Creates a new volume that containers can consume and store data in. If a name is not specified, Docker generates a random name. You create a volume and then configure the container to use it, for

Select a storage driver This page describes Docker’s storage driver feature. It lists the storage driver’s that Docker supports and the basic commands associated with managing them. Finally, this page provides guidance on choosing a storage driver. The material on this page is intended for readers who already have an understanding of the storage driver technology. A pluggable storage driver architecture Docker has a pluggable storage driver architecture. This gives you the flexibility to “plug

pull Usage: docker pull [OPTIONS] NAME[:TAG] | [REGISTRY_HOST[:REGISTRY_PORT]/]NAME[:TAG] Pull an image or a repository from the registry -a, --all-tags Download all tagged images in the repository --disable-content-trust=true Skip image verification --help Print usage Most of your images will be created on top of a base image from the Docker Hub registry. Docker Hub contains many pre-built images that you can pull and try without needing to defin

import Usage: docker import file|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. -c, --change=[] Apply specified Dockerfile instructions while importing the image --help Print usage -m, --message= Set commit message for imported image You can specify a URL or - (dash) to take data directly from STDIN. The URL can point to an archive (.tar,

Amazon CloudWatch Logs logging driver The awslogs logging driver sends container logs to Amazon CloudWatch Logs. Log entries can be retrieved through the AWS Management Console or the AWS SDKs and Command Line Tools. Usage You can configure the default logging driver by passing the --log-driver option to the Docker daemon: docker daemon --log-driver=awslogs You can set the logging driver for a specific container by using the --log-driver option to docker run: docker run --log-driver=awslogs ..

active See which machine is “active” (a machine is considered active if the DOCKER_HOST environment variable points to it). $ docker-machine ls NAME ACTIVE DRIVER STATE URL dev - virtualbox Running tcp://192.168.99.103:2376 staging * digitalocean Running tcp://203.0.113.81:2376 $ echo $DOCKER_HOST tcp://203.0.113.81:2376 $ docker-machine active staging