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

openSUSE and SUSE Linux Enterprise This page provides instructions for installing and configuring the latest Docker Engine software on openSUSE and SUSE systems. Note: You can also find bleeding edge Docker versions inside of the repositories maintained by the Virtualization:containers project on the Open Build Service. This project delivers also other packages that are related with the Docker ecosystem (for example, Docker Compose). Prerequisites You must be running a 64 bit architecture. op

create Create a machine. Requires the --driver flag to indicate which provider (VirtualBox, DigitalOcean, AWS, etc.) the machine should be created on, and an argument to indicate the name of the created machine. $ docker-machine create --driver virtualbox dev Creating CA: /home/username/.docker/machine/certs/ca.pem Creating client certificate: /home/username/.docker/machine/certs/cert.pem Image cache does not exist, creating it at /home/username/.docker/machine/cache... No default boot2docker i

Install Docker Machine On OS X and Windows, Machine is installed along with other Docker products when you install the Docker Toolbox. For details on installing Docker Toolbox, see the Mac OS X installation instructions or Windows installation instructions. If you want only Docker Machine, you can install the Machine binaries directly by following the instructions in the next section. You can find the latest versions of the binaries are on the docker/machine release page on GitHub. Installing

commit Usage: docker commit [OPTIONS] CONTAINER [REPOSITORY[:TAG]] Create a new image from a container's changes -a, --author="" Author (e.g., "John Hannibal Smith <hannibal@a-team.com>") -c, --change=[] Apply specified Dockerfile instructions while committing the image --help Print usage -m, --message="" Commit message -p, --pause=true Pause container during commit It can be useful to commit a container’s file changes or settings into a new image.

Docker default bridge network With the introduction of the Docker networks feature, you can create your own user-defined networks. The Docker default bridge is created when you install Docker Engine. It is a bridge network and is also named bridge. The topics in this section are related to interacting with that default bridge network. Understand container communication Legacy container links Binding container ports to the host Build your own bridge Configure container DNS Customize the docker0

Image management The Docker Engine provides a client which you can use to create images on the command line or through a build process. You can run these images in a container or publish them for others to use. Storing the images you create, searching for images you might want, or publishing images others might use are all elements of image management. This section provides an overview of the major features and products Docker provides for image management. Docker Hub The Docker Hub is responsi

Seccomp security profiles for Docker Secure computing mode (Seccomp) is a Linux kernel feature. You can use it to restrict the actions available within the container. The seccomp() system call operates on the seccomp state of the calling process. You can use this feature to restrict your application’s access. This feature is available only if Docker has been built with seccomp and the kernel is configured with CONFIG_SECCOMP enabled. To check if your kernel supports seccomp: $ cat /boot/config-

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

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