version Usage: docker version [OPTIONS] Show the Docker version information. -f, --format="" Format the output using the given go template --help Print usage By default, this will render all version information in an easy to read layout. If a format is specified, the given template will be executed instead. Go’s text/template package describes all the details of the format. Examples Default output: $ docker version Client: Version: 1.8.0 API version: 1.20 Go versi

Splunk logging driver The splunk logging driver sends container logs to HTTP Event Collector in Splunk Enterprise and Splunk Cloud. Usage You can configure the default logging driver by passing the --log-driver option to the Docker daemon: docker daemon --log-driver=splunk You can set the logging driver for a specific container by using the --log-driver option to docker run: docker run --log-driver=splunk ... Splunk options You can use the --log-opt NAME=VALUE flag to specify these additional

update Usage: docker update [OPTIONS] CONTAINER [CONTAINER...] Update configuration of one or more containers --help=false Print usage --blkio-weight=0 Block IO (relative weight), between 10 and 1000 --cpu-shares=0 CPU shares (relative weight) --cpu-period=0 Limit the CPU CFS (Completely Fair Scheduler) period --cpu-quota=0 Limit the CPU CFS (Completely Fair Scheduler) quota --cpuset-cpus="" CPUs in which to al

create — Create a discovery token The create command uses Docker Hub’s hosted discovery backend to create a unique discovery token for your cluster. For example: $ docker run --rm swarm create 86222732d62b6868d441d430aee4f055 Later, when you use manage or join to create Swarm managers and nodes, you use the discovery token in the <discovery> argument (e.g., token://86222732d62b6868d441d430aee4f055). The discovery backend registers each new Swarm manager and node that uses the token as a

history Usage: docker history [OPTIONS] IMAGE Show the history of an image -H, --human=true Print sizes and dates in human readable format --help Print usage --no-trunc Don't truncate output -q, --quiet Only show numeric IDs To see how the docker:latest image was built: $ docker history docker IMAGE CREATED CREATED BY SIZE COMMENT 3e23a5875458 8 days ago

Configuring and running Docker on various distributions After successfully installing Docker, the docker daemon runs with its default configuration. In a production environment, system administrators typically configure the docker daemon to start and stop according to an organization’s requirements. In most cases, the system administrator configures a process manager such as SysVinit, Upstart, or systemd to manage the docker daemon’s start and stop. Running the docker daemon directly The docker

stats Usage: docker stats [OPTIONS] [CONTAINER...] Display a live stream of one or more containers' resource usage statistics -a, --all Show all containers (default shows just running) --help Print usage --no-stream Disable streaming stats and only pull the first result The docker stats command returns a live data stream for running containers. To limit data to one or more specific containers, specify a list of container names or ids separated by a space. Yo

events Usage: docker events [OPTIONS] Get real time events from the server -f, --filter=[] Filter output based on conditions provided --help Print usage --since="" Show all events created since timestamp --until="" Stream events until this timestamp Docker containers report the following events: attach, commit, copy, create, destroy, die, exec_create, exec_start, export, kill, oom, pause, rename, resize, restart, start, stop, top, unpause, update Docke

Docker networks feature overview This sections explains how to use the Docker networks feature. This feature allows users to define their own networks and connect containers to them. Using this feature you can create a network on a single host or a network that spans across multiple hosts. Understand Docker container networks Work with network commands Get started with multi-host networking If you are already familiar with Docker’s default bridge network, docker0 that network continues to be

IBM Softlayer Create machines on Softlayer. You need to generate an API key in the softlayer control panel. Retrieve your API key $ docker-machine create --driver softlayer --softlayer-user=user --softlayer-api-key=KEY --softlayer-domain=domain vm Options: --softlayer-memory: Memory for host in MB. --softlayer-disk-size: A value of 0 will set the SoftLayer default. --softlayer-user: required Username for your SoftLayer account, api key needs to match this user. --softlayer-api-key: require