push Usage: docker push [OPTIONS] NAME[:TAG] Push an image or a repository to the registry --disable-content-trust=true Skip image signing --help Print usage Use docker push to share your images to the Docker Hub registry or to a self-hosted one. Killing the docker push process, for example by pressing CTRL-c while it is running in a terminal, will terminate the push operation. Registry credentials are managed by docker login.

ps Usage: docker ps [OPTIONS] List containers -a, --all Show all containers (default shows just running) -f, --filter=[] Filter output based on these conditions: - exited=<int> an exit code of <int> - label=<key> or label=<key>=<value> - status=(created|restarting|running|paused|exited) - name=<string> a container's name

pull Usage: docker pull [OPTIONS] NAME[:TAG] | [REGISTRY_HOST[:REGISTRY_PORT]/]NAME[:TAG] Pull an image or a repository from the registry -a, --all-tags Download all tagged images in the repository --disable-content-trust=true Skip image verification --help Print usage Most of your images will be created on top of a base image from the Docker Hub registry. Docker Hub contains many pre-built images that you can pull and try without needing to defin

port Usage: docker port [OPTIONS] CONTAINER [PRIVATE_PORT[/PROTO]] List port mappings for the CONTAINER, or lookup the public-facing port that is NAT-ed to the PRIVATE_PORT --help Print usage You can find out all the ports mapped by not specifying a PRIVATE_PORT, or just a specific mapping: $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES b650456536c7 busybo

pause Usage: docker pause [OPTIONS] CONTAINER [CONTAINER...] Pause all processes within a container --help Print usage The docker pause command uses the cgroups freezer to suspend all processes in a container. Traditionally, when suspending a process the SIGSTOP signal is used, which is observable by the process being suspended. With the cgroups freezer the process is unaware, and unable to capture, that it is being suspended, and subsequently resumed. See the cgroups freezer docu

network rm Usage: docker network rm [OPTIONS] NETWORK [NETWORK...] Deletes one or more networks --help Print usage Removes one or more networks by name or identifier. To remove a network, you must first disconnect any containers connected to it. To remove the network named ‘my-network’: $ docker network rm my-network To delete multiple networks in a single docker network rm command, provide multiple network names or ids. The following example deletes a network with id 3695c

docker network ls Usage: docker network ls [OPTIONS] Lists all the networks created by the user -f, --filter=[] Filter output based on conditions provided --help Print usage --no-trunc Do not truncate the output -q, --quiet Only display numeric IDs Lists all the networks the Engine daemon knows about. This includes the networks that span across multiple hosts in a cluster, for example: $ sudo docker network ls NETWORK ID NAME

network inspect Usage: docker network inspect [OPTIONS] NETWORK [NETWORK..] Displays detailed information on a network -f, --format= Format the output using the given go template. --help Print usage Returns information about one or more networks. By default, this command renders all results in a JSON object. For example, if you connect two containers to the default bridge network: $ sudo docker run -itd --name=container1 busybox f2870c98fd504370fb86e59f32cd0753b1ac9b69

Engine network driver plugins Docker Engine network plugins enable Engine deployments to be extended to support a wide range of networking technologies, such as VXLAN, IPVLAN, MACVLAN or something completely different. Network driver plugins are supported via the LibNetwork project. Each plugin is implemented as a “remote driver” for LibNetwork, which shares plugin infrastructure with Engine. Effectively, network driver plugins are activated in the same way as other plugins, and use the same ki

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