Dockerizing a Riak service The goal of this example is to show you how to build a Docker image with Riak pre-installed. Creating a Dockerfile Create an empty file called Dockerfile: $ touch Dockerfile Next, define the parent image you want to use to build your image on top of. We’ll use Ubuntu (tag: trusty), which is available on Docker Hub: # Riak # # VERSION 0.1.1 # Use the Ubuntu base image provided by dotCloud FROM ubuntu:trusty MAINTAINER Hector Castro hector@basho.com After that,

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

Log Tags The tag log option specifies how to format a tag that identifies the container’s log messages. By default, the system uses the first 12 characters of the container id. To override this behavior, specify a tag option: docker run --log-driver=fluentd --log-opt fluentd-address=myhost.local:24224 --log-opt tag="mailer" Docker supports some special template markup you can use when specifying a tag’s value: Markup Description {{.ID}} The first 12 characters of the container id. {{.FullID}}

Content trust in Docker When transferring data among networked systems, trust is a central concern. In particular, when communicating over an untrusted medium such as the internet, it is critical to ensure the integrity and the publisher of all the data a system operates on. You use Docker Engine to push and pull images (data) to a public or private registry. Content trust gives you the ability to verify both the integrity and the publisher of all the data received from a registry over any chan

manage — Create a Swarm manager Prerequisite: Before using manage to create a Swarm manager, establish a discovery backend as described in this discovery topic. The manage command creates a Swarm manager whose purpose is to receive commands on behalf of the cluster and assign containers to Swarm nodes. You can create multiple Swarm managers as part of a high-availability cluster. To create a Swarm manager, use the following syntax: $ docker run swarm manage [OPTIONS] <discovery> For exam

pull Usage: pull [options] [SERVICE...] Options: --ignore-pull-failures Pull what it can and ignores images with pull failures. Pulls service images.

Swarm and container networks Docker Swarm is fully compatible with Docker’s networking features. This includes the multi-host networking feature which allows creation of custom container networks that span multiple Docker hosts. Before using Swarm with a custom network, read through the conceptual information in Docker container networking. You should also have walked through the Get started with multi-host networking example. Create a custom network in a Swarm cluster Multi-host networks requi

run Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...] Run a command in 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=[] Add L

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

Deploying Notary Server with Compose The easiest way to deploy Notary Server is by using Docker Compose. To follow the procedure on this page, you must have already installed Docker Compose. Clone the Notary repository git clone git@github.com:docker/notary.git Build and start Notary Server with the sample certificates. docker-compose up -d For more detailed documentation about how to deploy Notary Server see the instructions to run a Notary service as well as https://github.com/docker/not