docker tag

tag Usage: docker tag [OPTIONS] IMAGE[:TAG] [REGISTRYHOST/][USERNAME/]NAME[:TAG] Tag an image into a repository --help Print usage You can group your images together using names and tags, and then upload them to Share Images via Repositories.

docker-compose build

build Usage: build [options] [SERVICE...] Options: --force-rm Always remove intermediate containers. --no-cache Do not use cache when building the image. --pull Always attempt to pull a newer version of the image. Services are built once and then tagged as project_service, e.g., composetest_db. If you change a service’s Dockerfile or the contents of its build directory, run docker-compose build to rebuild it.

docker export

export Usage: docker export [OPTIONS] CONTAINER Export the contents of a container's filesystem as a tar archive --help Print usage -o, --output="" Write to a file, instead of STDOUT The docker export command does not export the contents of volumes associated with the container. If a volume is mounted on top of an existing directory in the container, docker export will export the contents of the underlying directory, not the contents of the volume. Refer to Backup, restore

Installation on Debian

Debian Docker is supported on the following versions of Debian: Debian testing stretch (64-bit) Debian 8.0 Jessie (64-bit) Debian 7.7 Wheezy (64-bit) (backports required) Note: If you previously installed Docker using APT, make sure you update your APT sources to the new APT repository. Prerequisites Docker requires a 64-bit installation regardless of your Debian version. Additionally, your kernel must be 3.10 at minimum. The latest 3.10 minor version or a newer maintained version are also

docker diff

diff Usage: docker diff [OPTIONS] CONTAINER Inspect changes on a container's filesystem --help Print usage List the changed files and directories in a container᾿s filesystem There are 3 events that are listed in the diff: A - Add D - Delete C - Change For example: $ docker diff 7bb0e258aefe C /dev A /dev/kmsg C /etc A /etc/mtab A /go A /go/src A /go/src/github.com A /go/src/github.com/docker A /go/src/github.com/docker/docker A /go/src/github.com/docker/docker/.git ....

docker-machine env

env Set environment variables to dictate that docker should run a command against a particular machine. $ docker-machine env --help Usage: docker-machine env [OPTIONS] [arg...] Display the commands to set up the environment for the Docker client Description: Argument is a machine name. Options: --swarm Display the Swarm config instead of the Docker daemon --shell Force environment to be configured for a specified shell: [fish, cmd, powershell], default is sh/bash --unset, -u

docker-compose port

port Usage: port [options] SERVICE PRIVATE_PORT Options: --protocol=proto tcp or udp [default: tcp] --index=index index of the container if there are multiple instances of a service [default: 1] Prints the public port for a port binding.

Configure container DNS in user-defined networks

Embedded DNS server in user-defined networks The information in this section covers the embedded DNS server operation for containers in user-defined networks. DNS lookup for containers connected to user-defined networks works differently compared to the containers connected to default bridge network. Note: In order to maintain backward compatibility, the DNS configuration in default bridge network is retained with no behavioral change. Please refer to the DNS in default bridge network for more

Get started with multi-host networking

Get started with multi-host networking This article uses an example to explain the basics of creating a multi-host network. Docker Engine supports multi-host networking out-of-the-box through the overlay network driver. Unlike bridge networks, overlay networks require some pre-existing conditions before you can create one. These conditions are: Access to a key-value store. Docker supports Consul, Etcd, and ZooKeeper (Distributed store) key-value stores. A cluster of hosts with connectivity to t

OpenStack

OpenStack Create machines on OpenStack Mandatory: --openstack-auth-url: Keystone service base URL. --openstack-flavor-id or --openstack-flavor-name: Identify the flavor that will be used for the machine. --openstack-image-id or --openstack-image-name: Identify the image that will be used for the machine. $ docker-machine create --driver openstack vm Options: --openstack-active-timeout: The timeout in seconds until the OpenStack instance must be active. --openstack-availability-zone: The