Filters

Swarm filters Filters tell Docker Swarm scheduler which nodes to use when creating and running a container. Configure the available filters Filters are divided into two categories, node filters and container configuration filters. Node filters operate on characteristics of the Docker host or on the configuration of the Docker daemon. Container configuration filters operate on characteristics of containers, or on the availability of images on a host. Each filter has a name that identifies it. Th

FAQ

Frequently Asked Questions (FAQ) If you don’t see your question here, feel free to submit new ones to docs@docker.com. Or, you can fork the repo and contribute them yourself by editing the documentation sources. How much does Engine cost? Docker Engine is 100% free. It is open source, so you can use it without paying. What open source license are you using? We are using the Apache License Version 2.0, see it here: https://github.com/docker/docker/blob/master/LICENSE Does Docker run on Mac OS X

Extending Services in Compose

Extending services and Compose files Compose supports two methods of sharing common configuration: Extending an entire Compose file by using multiple Compose files Extending individual services with the extends field Multiple Compose files Using multiple Compose files enables you to customize a Compose application for different environments or different workflows. Understanding multiple Compose files By default, Compose reads two files, a docker-compose.yml and an optional docker-compose.ov

Exoscale

Exoscale Create machines on exoscale. Get your API key and API secret key from API details and pass them to machine create with the --exoscale-api-key and --exoscale-api-secret-key options. $ docker-machine create --driver exoscale --exoscale-api-key=API --exoscale-api-secret-key=SECRET vm Options: --exoscale-url: Your API endpoint. --exoscale-api-key: required Your API key. --exoscale-api-secret-key: required Your API secret key. --exoscale-instance-profile: Instance profile. --exoscale-

Extending Engine with plugins

Understand Engine plugins You can extend the capabilities of the Docker Engine by loading third-party plugins. This page explains the types of plugins and provides links to several volume and network plugins for Docker. Types of plugins Plugins extend Docker’s functionality. They come in specific types. For example, a volume plugin might enable Docker volumes to persist across multiple Docker hosts and a network plugin might provide network plumbing. Currently Docker supports authorization, vol

Example: Use Docker Machine to provision cloud hosts

Example: Use Docker Machine to provision cloud hosts Docker Machine driver plugins are available for many cloud platforms, so you can use Machine to provision cloud hosts. When you use Docker Machine for provisioning, you create cloud hosts with Docker Engine installed on them. You’ll need to install and run Docker Machine, and create an account with the cloud provider. Then you provide account verification, security credentials, and configuration options for the providers as flags to docker-ma

Example: Manual install on cloud provider

Example: Manual install on cloud provider You can install Docker Engine directly to servers you have on cloud providers. This example shows how to create an Amazon Web Services (AWS) EC2 instance, and install Docker Engine on it. You can use this same general approach to create Dockerized hosts on other cloud providers. Step 1. Sign up for AWS If you are not already an AWS user, sign up for AWS to create an account and get root access to EC2 cloud computers. If you have an Amazon account, you

Evaluate Swarm in a sandbox

Evaluate Swarm in a sandbox This getting started example shows you how to create a Docker Swarm, the native clustering tool for Docker. You’ll use Docker Toolbox to install Docker Machine and some other tools on your computer. Then you’ll use Docker Machine to provision a set of Docker Engine hosts. Lastly, you’ll use Docker client to connect to the hosts, where you’ll create a discovery token, create a cluster of one Swarm manager and nodes, and manage the cluster. When you finish, you’ll have

ETW logging driver

ETW logging driver The ETW logging driver forwards container logs as ETW events. ETW stands for Event Tracing in Windows, and is the common framework for tracing applications in Windows. Each ETW event contains a message with both the log and its context information. A client can then create an ETW listener to listen to these events. The ETW provider that this logging driver registers with Windows, has the GUID identifier of: {a3693192-9ed6-46d2-a981-f8226c8363bd}. A client creates an ETW liste

Environment file

Environment file Compose supports declaring default environment variables in an environment file named .env placed in the folder docker-compose command is executed from (current working directory). Compose expects each line in an env file to be in VAR=VAL format. Lines beginning with # (i.e. comments) are ignored, as are blank lines. Note: Values present in the environment at runtime will always override those defined inside the .env file. Similarly, values passed via command-line arguments ta