info Usage: docker info [OPTIONS] Display system-wide information --help Print usage For example: $ docker -D info Containers: 14 Running: 3 Paused: 1 Stopped: 10 Images: 52 Server Version: 1.9.0 Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 545 Dirperm1 Supported: true Execution Driver: native-0.2 Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge null host Kernel Version: 3.19.0-22-generic O

list — List the nodes in a cluster Use list to display a list of the nodes in a cluster. To list the nodes in a cluster, use the following syntax: docker run swarm list [OPTIONS] <discovery> The following examples show a few different syntaxes for the <discovery> argument: etcd: swarm list etcd://<etcd_addr1>,<etcd_addr2>/<optional path prefix> <node_ip:port> Consul: swarm list consul://<consul_addr>/<optional path prefix> <node_ip:port>

unpause Usage: unpause [SERVICE...] Unpauses paused containers of a service.

Docker Remote API v1.22 1. Brief introduction The Remote API has replaced rcli. The daemon listens on unix:///var/run/docker.sock but you can Bind Docker to another host/port or a Unix socket. The API tends to be REST. However, for some complex commands, like attach or pull, the HTTP connection is hijacked to transport stdout, stdin and stderr. When the client API version is newer than the daemon’s, these calls return an HTTP 400 Bad Request error message. 2. Endpoints 2.1 Containers List con

Evaluate Swarm in a sandbox This getting started example shows you how to create a Docker Swarm, the native clustering tool for Docker. You’ll use Docker Toolbox to install Docker Machine and some other tools on your computer. Then you’ll use Docker Machine to provision a set of Docker Engine hosts. Lastly, you’ll use Docker client to connect to the hosts, where you’ll create a discovery token, create a cluster of one Swarm manager and nodes, and manage the cluster. When you finish, you’ll have

Use Docker Machine to provision hosts on cloud providers Docker Machine driver plugins are available for many cloud platforms, so you can use Machine to provision cloud hosts. When you use Docker Machine for provisioning, you create cloud hosts with Docker Engine installed on them. You’ll need to install and run Docker Machine, and create an account with the cloud provider. Then you provide account verification, security credentials, and configuration options for the providers as flags to docke

inspect Usage: docker inspect [OPTIONS] CONTAINER|IMAGE [CONTAINER|IMAGE...] Return low-level information on a container or image -f, --format="" Format the output using the given go template --help Print usage --type=container|image Return JSON for specified type, permissible values are "image" or "container" -s, --size Display total file sizes if the type is container By default, this will render all results in a JSON

Frequently Asked Questions (FAQ) If you don’t see your question here, feel free to submit new ones to docs@docker.com. Or, you can fork the repo and contribute them yourself by editing the documentation sources. How much does Engine cost? Docker Engine is 100% free. It is open source, so you can use it without paying. What open source license are you using? We are using the Apache License Version 2.0, see it here: https://github.com/docker/docker/blob/master/LICENSE Does Docker run on Mac OS X

CRUX Linux Installing on CRUX Linux can be handled via the contrib ports from James Mills and are included in the official contrib ports: docker The docker port will build and install the latest tagged version of Docker. Installation Assuming you have contrib enabled, update your ports tree and install docker: $ sudo prt-get depinst docker Kernel requirements To have a working CRUX+Docker Host you must ensure your Kernel has the necessary modules enabled for the Docker Daemon to function cor

ip Get the IP address of one or more machines. $ docker-machine ip dev 192.168.99.104 $ docker-machine ip dev dev2 192.168.99.104 192.168.99.105