Docker Remote API v1.21 1. Brief introduction The Remote API has replaced rcli. The daemon listens on unix:///var/run/docker.sock but you can Bind Docker to another host/port or a Unix socket. The API tends to be REST. However, for some complex commands, like attach or pull, the HTTP connection is hijacked to transport stdout, stdin and stderr. When the client API version is newer than the daemon’s, these calls return an HTTP 400 Bad Request error message. 2. Endpoints 2.1 Containers List con

Troubleshoot the application It’s a fact of life that things fail. With this in mind, it’s important to understand what happens when failures occur and how to mitigate them. The following sections cover different failure scenarios: Swarm manager failures Consul (discovery backend) failures Interlock load balancer failures Web (voting-app) failures Redis failures Worker (vote-worker) failures Postgres failures Results-app failures Infrastructure failures Swarm manager failures In it’s current

Hello world in a container So what’s this Docker thing all about? Docker allows you to run applications, worlds you create, inside containers. Running an application inside a container takes a single command: docker run. Note: Depending on your Docker system configuration, you may be required to preface each docker command on this page with sudo. To avoid this behavior, your system administrator can create a Unix group called docker and add users to it. Run a Hello world Let’s run a hello wor

Docker Remote API v1.18 1. Brief introduction The Remote API has replaced rcli. The daemon listens on unix:///var/run/docker.sock but you can Bind Docker to another host/port or a Unix socket. The API tends to be REST, but for some complex commands, like attach or pull, the HTTP connection is hijacked to transport STDOUT, STDIN and STDERR. 2. Endpoints 2.1 Containers List containers GET /containers/json List containers Example request: GET /containers/json?all=1&before=8dfafdbc3a40&am

Bind container ports to the host The information in this section explains binding container ports within the Docker default bridge. This is a bridge network named bridge created automatically when you install Docker. Note: The Docker networks feature allows you to create user-defined networks in addition to the default bridge network. By default Docker containers can make connections to the outside world, but the outside world cannot connect to containers. Each outgoing connection will appear

Docker and ZFS in practice ZFS is a next generation filesystem that supports many advanced storage technologies such as volume management, snapshots, checksumming, compression and deduplication, replication and more. It was created by Sun Microsystems (now Oracle Corporation) and is open sourced under the CDDL license. Due to licensing incompatibilities between the CDDL and GPL, ZFS cannot be shipped as part of the mainline Linux kernel. However, the ZFS On Linux (ZoL) project provides an out-o

CLI Environment Variables Several environment variables are available for you to configure the Docker Compose command-line behaviour. Variables starting with DOCKER_ are the same as those used to configure the Docker command-line client. If you’re using docker-machine, then the eval "$(docker-machine env my-docker-vm)" command should set them to their correct values. (In this example, my-docker-vm is the name of a machine you created.) Note: Some of these variables can also be provided using a

rm Usage: rm [options] [SERVICE...] Options: -f, --force Don't ask to confirm removal -v Remove any anonymous volumes attached to containers -a, --all Also remove one-off containers created by docker-compose run Removes stopped service containers. By default, anonymous volumes attached to containers will not be removed. You can override this with -v. To list all volumes, use docker volume ls. Any data which is not in a volume will be lost.

Docker Remote API client libraries These libraries make it easier to build applications on top of the Docker Remote API with various programming languages. They have not been tested by the Docker maintainers for compatibility, so if you run into any issues, file them with the library maintainers. Language/Framework Name Repository C# Docker.DotNet https://github.com/ahmetalpbalkan/Docker.DotNet C++ lasote/docker_client https://github.com/lasote/docker_client Erlang erldocker https://github.com/

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