docker history

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

Network configuration

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

Machine concepts and help

Understand Machine concepts and get help Docker Machine allows you to provision Docker machines in a variety of environments, including virtual machines that reside on your local system, on cloud providers, or on bare metal servers (physical computers). Docker Machine creates a Docker host, and you use the Docker Engine client as needed to build images and create containers on the host. Drivers for creating machines To create a virtual machine, you supply Docker Machine with the name of the dri

Configuring and running Docker

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

API response codes

Understand the Swarm vs. Engine response codes Docker Engine provides a REST API for making calls to the Engine daemon. Docker Swarm allows a caller to make the same calls to a cluster of Engine daemons. While the API calls are the same, the API response status codes do differ. This document explains the differences. Four methods are included, and they are GET, POST, PUT and DELETE. The comparison is based on api v1.22, and all Docker Status Codes in api v1.22 are referenced from docker-remote-

docker network disconnect

network disconnect Usage: docker network disconnect [OPTIONS] NETWORK CONTAINER Disconnects a container from a network -f, --force Force the container to disconnect from a network --help Print usage Disconnects a container from a network. The container must be running to disconnect it from the network. $ docker network disconnect multi-host-network container1 Related information network inspect network connect network create network ls network rm Understand Docker

docker events

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 version

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

Migrate from Boot2Docker to Machine

Migrate from Boot2Docker to Docker Machine If you were using Boot2Docker previously, you have a pre-existing Docker boot2docker-vm VM on your local system. To allow Docker Machine to manage this older VM, you must migrate it. Open a terminal or the Docker CLI on your system. Type the following command. $ docker-machine create -d virtualbox --virtualbox-import-boot2docker-vm boot2docker-vm docker-vm Use the docker-machine command to interact with the migrated VM. Subcommand comparison The d

Driver options and operating system defaults

Driver options and operating system defaults When Docker Machine provisions containers on local network provider or with a remote, cloud provider such as Amazon Web Services, you must define both the driver for your provider and a base operating system. There are over 10 supported drivers and a generic driver for adding machines for other providers. Each driver has a set of options specific to that provider. These options provide information to machine such as connection credentials, ports, and