start Usage: start [SERVICE...] Starts existing containers for a service.

Using Puppet Note: Please note this is a community contributed installation path. The only official installation is using the Ubuntu installation path. This version may sometimes be out of date. Requirements To use this guide you’ll need a working installation of Puppet from Puppet Labs . The module also currently uses the official PPA so only works with Ubuntu. Installation The module is available on the Puppet Forge and can be installed using the built-in module tool. $ puppet module instal

Oracle Linux Docker is supported Oracle Linux 6 and 7. You do not require an Oracle Linux Support subscription to install Docker on Oracle Linux. Prerequisites Due to current Docker limitations, Docker is only able to run only on the x86_64 architecture. Docker requires the use of the Unbreakable Enterprise Kernel Release 4 (4.1.12) or higher on Oracle Linux. This kernel supports the Docker btrfs storage engine on both Oracle Linux 6 and 7. Install Note: The procedure below installs binaries b

Deploy your infrastructure In this step, you create several Docker hosts to run your application stack on. Before you continue, make sure you have taken the time to learn the application architecture. About these instructions This example assumes you are running on a Mac or Windows system and enabling Docker Engine docker commands by provisioning local VirtualBox virtual machines thru Docker Machine. For this evaluation installation, you’ll need 6 (six) VirtualBox VMs. While this example uses D

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

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

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 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

Fluentd logging driver The fluentd logging driver sends container logs to the Fluentd collector as structured log data. Then, users can use any of the various output plugins of Fluentd to write these logs to various destinations. In addition to the log message itself, the fluentd log driver sends the following metadata in the structured log message: Field Description container_id The full 64-character container ID. container_name The container name at the time it was started. If you use docker