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

rmi Usage: docker rmi [OPTIONS] IMAGE [IMAGE...] Remove one or more images -f, --force Force removal of the image --help Print usage --no-prune Do not delete untagged parents You can remove an image using its short or long ID, its tag, or its digest. If an image has one or more tag referencing it, you must remove all of them before the image is removed. Digest references are removed automatically when an image is removed by tag. $ docker images REPOSITO

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

Docker Swarm Docker Swarm overview How to get Docker Swarm Evaluate Swarm in a sandbox Plan for Swarm in production Build a Swarm cluster for production Try Swarm at scale Overview Swarm with TLS Configure Docker Swarm for TLS Docker Swarm Discovery High availability in Docker Swarm Swarm and container networks Advanced Scheduling Provision a Swarm cluster with Docker Machine Docker Swarm API

Swarm Rescheduling You can set recheduling policies with Docker Swarm. A rescheduling policy determines what the Swarm scheduler does for containers when the nodes they are running on fail. Rescheduling policies You set the reschedule policy when you start a container. You can do this with the reschedule environment variable or the com.docker.swarm.reschedule-policies label. If you don’t specify a policy, the default rescheduling policy is off which means that Swarm does not restart a container

create Creates containers for a service. Usage: create [options] [SERVICE...] Options: --force-recreate Recreate containers even if their configuration and image haven't changed. Incompatible with --no-recreate. --no-recreate If containers already exist, don't recreate them. Incompatible with --force-recreate. --no-build Don't build an image, even if it's missing. --build Build imag

Manage data in containers So far you’ve been introduced to some basic Docker concepts, seen how to work with Docker images as well as learned about networking and links between containers. In this section you’re going to learn how you can manage data inside and between your Docker containers. You’re going to look at the two primary ways you can manage data with Docker Engine. Data volumes Data volume containers Data volumes A data volume is a specially-designated directory within one or more

Create a base image So you want to create your own Base Image? Great! The specific process will depend heavily on the Linux distribution you want to package. We have some examples below, and you are encouraged to submit pull requests to contribute new ones. Create a full image using tar In general, you’ll want to start with a working machine that is running the distribution you’d like to package as a base image, though that is not required for some tools like Debian’s Debootstrap, which you can

unpause Usage: docker unpause [OPTIONS] CONTAINER [CONTAINER...] Unpause all processes within a container --help Print usage The docker unpause command uses the cgroups freezer to un-suspend all processes in a container. See the cgroups freezer documentation for further details.

create Creates a new container. Usage: docker create [OPTIONS] IMAGE [COMMAND] [ARG...] Create a new container -a, --attach=[] Attach to STDIN, STDOUT or STDERR --add-host=[] Add a custom host-to-IP mapping (host:ip) --blkio-weight=0 Block IO weight (relative weight) --blkio-weight-device=[] Block IO weight (relative device weight, format: `DEVICE_NAME:WEIGHT`) --cpu-shares=0 CPU shares (relative weight) --cap-add=[]