1, Docker-Compose Profile
Docker Docker-Compose official project is an open source project, responsible for fast layout of Docker container cluster.
Docker-Compose will be managed by a container divided into three levels, namely the project (project), service (service) and container (container). All files (docker-compose.yml, extends file or environment variable file, etc.) in Docker-Compose run up a project directory, in the absence of special designated project name is the name of the current directory. A project which may comprise a plurality of services, each defined image container runs, parameters dependent. A service which may include multiple container instance, Docker-Compose does not solve the problem of load balancing, and therefore need to use other tools to achieve service discovery and load balancing.
Docker-Compose project configuration files by default docker-compose.yml, can COMPOSE_FILE through the environment variable or -f parameter custom configuration file, which defines several services that depend on each service and run a container.
Dockerfile you use a template file, allowing users to easily define a single application container. At work, often encounter case to complete a task requiring multiple containers with each other. For example, to implement a Web project, in addition to Web services container itself, often also need to add the back-end database services container, even including load balancing containers.
Compose application allows the user to define a group of containers associated by a single docker-compose.yml template file (YAML format) for a project (project).
Docker-Compose project written by Python, call the API Docker service provided to manage the container. Therefore, as long as the operating platform to support Docker API, you can manage to orchestrate use Compose thereon.
2, Docker-Compose installation
Installation a:
Download Docker-Compose:
sudo curl -L https://github.com/docker/compose/releases/download/1.23.0-rc3/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-composeInstallation Docker-Compose: sudo chmod +x /usr/local/bin/docker-compose
View Version: docker-compose version
Installation Method Two:
Installation pip
yum -y install epel-release
yum -y install python-pipConfirm the version pip --version
update pip pip install --upgrade pip
install docker-compose pip install docker-compose
view the version docker-compose version
installed completion tool:
In order to facilitate input commands can also be installed Docker completions tools help to quickly enter the command prompt:
install yum install bash-completion
download docker-compose scripts
curl -L https://raw.githubusercontent.com/docker/compose/$(docker-compose version --short)/contrib/completion/bash/docker-compose > /etc/bash_completion.d/docker-compose3, Docker-Compose uninstall
If it is a binary package installed, you can delete the binary files: sudo rm /usr/local/bin/docker-compose
If you via Python pip tools installed, then execute the following command to delete:sudo pip uninstall docker-compose
Two, Docker-Compose common commands
1, Docker-Compose Format
docker-compose [-f <arg>...] [options] [COMMAND] [ARGS...]Command options are as follows:
-f, -file FILE specify Compose a template file, the default is docker-compose.yml, can be specified multiple times.
-p, -project-name NAME specify the project name, the default directory name will be used as the project name.
Docker network using the back-end characteristics pluggable -x-network-driver (version requires Docker 1.9+)
driving -x-network-driver DRIVER backend network specified, the default is Bridge (version requires Docker 1.9+)
-verbose more output multi debugging information
-v, -version Print version and exit
2、docker-compose up
docker-compose up [options] [--scale SERVICE=NUM...] [SERVICE...]The options are:
-d container service running in the background
without the use of color -no-color to distinguish between different services control output
container -no-deps not start the service linked
-force-recreate forced to re-create the container, not with -no- recreate use
-no-recreate If the container already exists, it is not re-created, can not be used with the -force-recreate
service mirroring -no-build does not automatically build missing
-build mirror before starting to build a service container
-abort-on- container-exit stop all container, a container is stopped if any, can not be used in conjunction with -d
-t, -timeout tIMEOUT timeout to stop container time (default is 10 seconds)
-remove-Orphans delete a service is not defined in the compose documents the container
-scale sERVICE = number of container set the service to run NUM, will compose the scale covering parameters specified by the docker-compose up
start all the services docker-compose up -d
in the background all start the service
-f specify the Compose a template file, the default is docker-compose.yml, You can specify multiple times.docker-compose -f docker-compose.yml up -d
3、docker-compose ps
docker-compose ps [options] [SERVICE...]docker-compose ps
All items listed in the current container
4、docker-compose stop
docker-compose stop [options] [SERVICE...]
Options include:
-t, -timeout TIMEOUT timeout to stop container time (default is 10 seconds) docker-compose stop
stop the container is running, you can start again by docker-compose start
5、docker-compose -h
docker-compose -h
View Help
6、docker-compose down
docker-compose down [options]
Stop and remove container, network volumes, mirrored.
Options include:
-rmi of the type, remove the mirror, the type must be: all, all mirrored delete compose defined in the file; local, remove the mirror image called empty
-v, -volumes, delete the already defined in the file and compose Anonymous data volume on the attached container
-remove-orphans, remove the service is not defined in the compose container docker-compose down
deactivate and remove all container network-related
7、docker-compose logs
docker-compose logs [options] [SERVICE...]
View the output service container. By default, docker-compose the output will be different services use different colors to distinguish. Color can be closed by -no-color. docker-compose logs
Look at the output of the service vessel
8、docker-compose build
docker-compose build [options] [--build-arg key=val...] [SERVICE...]
Building (rebuilding) service container project.
Options include:
-compress gzip compression by constructing upper and lower environmental
-force-rm delete build temporary container during
-no-cache building process does not use mirrored cache
-pull always try to get an updated version of the image by the action of pulling
-m, -memory MEM container is provided for the construction of the memory size
-build-arg key = val service provided build-time variable
service container once constructed, will bring a tag name. You can always run docker-compose build under the project to rebuild the directory service
9、docker-compose pull
docker-compose pull [options] [SERVICE...]
Pull service dependent mirror.
Options include:
-ignore-pull-failures, ignore the error pull mirroring process
-parallel, multiple mirror while pulling
-quiet, pull mirroring process does not print progress information docker-compose pull
pull service dependent mirror
10、docker-compose restart
docker-compose restart [options] [SERVICE...]
Restart project services.
Options include:
-t, -timeout before TIMEOUT, specify the restart timeout to stop the vessel (the default is 10 seconds) docker-compose restart
to restart the project in the service
11、docker-compose rm
docker-compose rm [options] [SERVICE...]
Delete all service container (stop state).
The options are:
-f, -force, forced to delete, including non-stop state of the container
-v, delete container mounted data volumes docker-compose rm
to delete all service container (stop state). It is recommended to perform docker-compose stop command to stop the vessel.
12、docker-compose start
docker-compose start [SERVICE...]docker-compose start
Start the service container that already exists.
13、docker-compose run
docker-compose run [options] [-v VOLUME...] [-p PORT...] [-e KEY=VAL...] SERVICE [COMMAND] [ARGS...]
Execute a command on the specified service. docker-compose run ubuntu ping www.baidu.com
Execute a ping command in the specified container.
14、docker-compose scale
docker-compose scale web=3 db=2
Set the number of containers specified service running. To set the number of parameters by num service =
15、docker-compose pause
docker-compose pause [SERVICE...]
Pause a service container
16、docker-compose kill
docker-compose kill [options] [SERVICE...]
By sending a signal to forcibly stop the services SIGKILL container.
Support signal transmitted through -s specified parameters, such as command transmitting SIGINT signal by:docker-compose kill -s SIGINT
17, consists dokcer-config
docker-compose config [options]
Verify compose and view the file configuration.
Options include:
-resolve-Image-Digests it is possible to label image labeled as a digest
-q, -quiet only verify the configuration, is not output. When properly configured, does not output anything, when the file configuration errors, output an error message
-services print service name, one per line
-volumes print data volume name, one per line
18、docker-compose create
docker-compose create [options] [SERVICE...]
Create a container for the service.
Options include:
-force-recreate: to re-create the container, even if the configuration has not changed and mirrors, is not compatible with -no-recreate parameters
-no-recreate: If the container already exists, do not need to re-create, is not compatible with -force-recreate parameters
-no -build: Do not create a mirror, even if the lack of
-build: create a container before, generated image
19、docker-compose exec
docker-compose exec [options] SERVICE COMMAND [ARGS...]
The options are:
-d separate mode, command running in the background.
-Privileged get privileges.
-User USER Specifies the user runs.
-T Disable allocation TTY, default docker-compose exec assignment TTY.
-Index = index, when a service has a plurality of containers, this parameter can be found to any service in the service, for example: docker-compose exec -index = 1 web / bin / bash, web service comprising a plurality of containers
20、docker-compose port
docker-compose port [options] SERVICE PRIVATE_PORT
Public display port a container port mapping.
Options include:
--protocol = proto, designated port protocol, TCP (default) or UDP
-index = index, if you agree there are multiple service containers, container specified number of command object (default is 1)
21、docker-compose push
docker-compose push [options] [SERVICE...]
Push service according to the Mirror.
Options include:
-ignore the Push-push-mirroring process failures ignore errors
22、docker-compose stop
docker-compose stop [options] [SERVICE...]
Display case each container process running.
23、docker-compose unpause
docker-compose unpause [SERVICE...]
Restore service in a suspended state.
24、docker-compose version
docker-compose version
Print version information.
Three, Docker-Compose a template file
1, Docker-Compose template file Profile
Compose application allows the user to define a group of containers associated by a docker-compose.yml template file (YAML format) for a project (project).
Compose a template file is the definition of service, and network volumes YAML file. Compose a template file in the default path is docker-compose.yml in the current directory, you can use .yml or .yaml as the file extension.
Docker-Compose standard template file should contain version, services, networks of three parts, the most critical services and networks is in two parts.
version: '2'
services:
web:
image: dockercloud/hello-world ports: - 8080 networks: - front-tier - back-tier redis: image: redis links: - web networks: - back-tier lb: image: dockercloud/haproxy ports: - 80:80 links: - web networks: - front-tier - back-tier volumes: - /var/run/docker.sock:/var/run/docker.sock networks: front-tier: driver: bridge back-tier: driver: bridgeCompose There are three versions Version 1, Version 2, Version 3, Compose distinguish Version 1 and Version 2 (Compose 1.6.0 +, Docker Engine 1.10.0+). Version 2 supports more instructions. Version 1 will be abandoned in the future.
2、image
image is a mirror image ID or name specified services. If the mirror does not exist locally, Compose will try to pull the mirror.
services:
web:
image: hello-world3、build
In addition to the service based on the specified image can also be based on a Dockerfile, while using up to start the implementation of building tasks, build tag is build, you can specify the path to the folder where Dockerfile. Compose use Dockerfile will automatically build the mirror, and then use the image to start the service container. build: /path/to/build/dir
It may be a relative path, as long as it can read the context determination Dockerfile. build: ./dir
Setting context root, and then subject to the specified directory Dockerfile.
build:
context: ../
dockerfile: path/of/Dockerfilebuild is a directory, if you want to specify Dockerfile file needs to specify the use of dockerfile tag in the child tag build tag.
If you specify the image and build two labels at the same time, the Compose builds mirror and the mirror image name specified value name.
4、context
context options may be Dockerfile file path, may also be a link to a git repository url, when the value of providing a relative path, the path is resolved relative to write the file, this directory is sent to the Docker daemon context
build:
context: ./dir5、dockerfile
Use dockerfile files to build, you must specify the build path
build:
context: .
dockerfile: Dockerfile-alternatedockerfile instruction can not be used simultaneously with the image, or Compose the uncertainty to generate the final image depending on which services directive.
6、command
Use command can override the default command is executed after the vessel started.command: bundle exec thin -p 3000
7、container_name
Compose container name format is: <project name> <service name> <number>
can customize the project name, service name, but if you want full control of the vessel name, you can use the tag to specify:container_name: app
8、depends_on
When using Compose, the biggest advantage is to play a small start-up command, but the order of the general project started by the container is required, if the direct start from top to bottom of the container, because the container will inevitably depend on the issue failed to start. Such as starting an application container, the container will use the database and quit because they can not when we do not start the database container. depends_on label for container-dependent solve, the problem has started in.
version: '2'
services:
web:
build: .
depends_on:
- db
- redis
redis:
image: redis
db:
image: postgresAbove YAML file defines the container will first start redis and db two services, and finally start the web service.
9、pid
pid: "host"
The PID PID mode is set to host mode, shared with the host system processes namespace. Pid will be able to use the container tag access and manipulate the namespace of the host and other containers.
10、ports
ports for mapping the label port.
Use HOST: CONTAINER format or just specified container port, port mapping host random chance.
ports:
- "3000"
- "8000:8000"
- "49100:22" - "127.0.0.1:8001:8001"When HOST: CONTAINER port mapped format, if the container is smaller than the port 60 can get incorrect results obtained, as will parse YAML xx: yy This digital format is 60-ary. It is recommended that the use of string format.
11、extra_hosts
Add tags host name, will add some records in the / etc / hosts file.
extra_hosts:
- "somehost:162.242.195.82"
- "otherhost:50.31.209.229"After you start to see inside the container hosts:
162.242.195.82 somehost
50.31.209.229 otherhost12、volumes
A directory or mount an existing data volume container, can be used directly [HOST: CONTAINER] format, or use [HOST: CONTAINER: ro] format, the latter to the container, the data volume is read-only, can be effectively protection of the host file system.
Compose specified path data volume may be a relative path, use. Or .. to specify the relative directory.
Data volume format may be the following forms:
volumes:
// 只是指定一个路径，Docker 会自动在创建一个数据卷（这个路径是容器内部的）。
- /var/lib/mysql
// 使用绝对路径挂载数据卷
- /opt/data:/var/lib/mysql // 以 Compose 配置文件为中心的相对路径作为数据卷挂载到容器。 - ./cache:/tmp/cache // 使用用户的相对路径（~/ 表示的目录是 /home/<用户目录>/ 或者 /root/）。 - ~/configs:/etc/configs/:ro // 已经存在的命名的数据卷。 - datavolume:/var/lib/mysqlIf no path host can specify a volume_driver.volume_driver: mydriver
13、volumes_from
Mount it from another service or data volume container:
volumes_from:
- service_name
- container_name14、dns
Custom DNS server. Can be a value, it can be a list.
dns：8.8.8.8
dns： - 8.8.8.8 - 9.9.9.915、dns_search
Configuring DNS search domains. Can be a value, it can be a list.
dns_search：example.com
dns_search：
- domain1.example.com - domain2.example.com16、entrypoint
There are known in Dockerfile ENTRYPOINT instruction in an instruction to specify an access point.
The access point may be defined docker-compose.yml, the cover defined in Dockerfile:entrypoint: /code/entrypoint.sh
17、env_file
You can define a special file stored in the variable docker-compose.yml in.
If the specified configuration file docker-compose -f FILE, then the path will be used env_file profile path.
If there are conflicting instructions environment variable name, the latter shall prevail. Format is as follows: env_file: .env
or according to a plurality of docker-compose.yml:
env_file:
- ./common.env
- ./apps/web.env
- /opt/secrets.envIf you have build operations in the configuration file, variable and not enter the build process.
18、cap_add
Adds the specified container core capability (capacity).
Let vessel has all the ability to specify:
cap_add:
- ALL19、cap_drop
Ability to remove the core specified container (capacity).
Remove NET_ADMIN capability can be specified:
cap_drop:
- NET_ADMIN20、cgroup_parent
Created a cgroup group name cgroups_1:cgroup_parent: cgroups_1
21、devices
Specify the device mapping relationship, such as:
devices:
- "/dev/ttyUSB1:/dev/ttyUSB0"22、expose
Exposure to port, but does not map to the host, allowing only access to services that can be connected. Designated internal port can only be a parameter, as follows:
expose:
- "3000"
- "8000"23、extends
Be extended based on other template files. For example, for webapp service defines a basic template file for the common.yml:
# common.yml
webapp:
build: ./webapp
environment:
- DEBUG=false
- SEND_EMAILS=falseThen write a new development.yml file, use the webapp service common.yml extended:
# development.yml
web:
extends:
file: common.yml
service: webapp
ports:
- "8000:8000"
links:
- db
environment:
- DEBUG=true
db:
image: mysqlThe latter will automatically inherit the webapp service and environment variables defined in common.yml.
extends following restrictions:
A, to avoid cycle-dependent
B, and the container extends not inherit data volumes and resource links volumes_from defined in
recommendation defines only some of which may mirror and shared environment variables based on the template, the template in the extension specify application variables, links, data volume and other information
24、external_links
Links to external containers docker-compose.yml, the outer container may be non Compose management.
external_links:
- redis_1
- project_db_1:mysql - project_db_1:postgresql25、labels
Docker adding metadata (Metadata) information container. For example, the container may be added as auxiliary information Description:
labels：
com.startupteam.description: "webapp for a strtup team"26、links
Links to other services in the container. Service name (alias simultaneously), or "Service Name: Alias Service" (e.g. SERVICE: ALIAS), for example:
links:
- db
- db:database - redisServices will automatically use aliases in the container / etc / hosts was created. E.g:
172.17.2.186 db
172.17.2.186 database 172.17.2.187 redis27、log_driver
Specifies the log drive type. Currently supports three log drive type:
log_driver: "json-file"
log_driver: "syslog"
log_driver: "none"28、log_opt
Log drive parameters. E.g:
log_driver: "syslog"log_opt:
syslog-address: "tcp://192.168.0.42:123"29、net
Set network mode.
net: "bridge"
net: "none"
net: "host"30、security_opt
The default template attribute specifies the container label (label) mechanism (user, role, type, level, etc.). For example, the configuration of user names and roles label name:
security_opt:
- label:user:USER - label:role:ROLE31, environment variables
Environment variables can be used to configure the behavior of Docker-Compose.
COMPOSE_PROJECT_NAME
item name to be added before the start through every container Compose, the default is the name of the current working directory.
COMPOSE_FILE
set the path docker-compose.yml template file. The default path is the current working directory.
DOCKER_HOST
set the address of Docker daemon. ///Var/run/docker.sock: use the unix default. DOCKER_TLS_VERIFY
If the setting is not empty, then interact with the Docker daemon via TLS.
DOCKER_CERT_PATH
configuration validation path (ca.pem, cert.pem and the key.pem) files required for TLS communication, the default is ~ / .docker.
Four, Docker-Compose a template file example
1, write docker-compose the template file
docker-compose.yaml file as follows:
version: '2'
services:
web1:
image: nginx
ports:
- "6061:80"
container_name: "web1"
networks:
- dev
web2:
image: nginx
ports:
- "6062:80" container_name: "web2" networks: - dev - pro web3: image: nginx ports: - "6063:80" container_name: "web3" networks: - pro networks: dev: driver: bridge pro: driver: bridge #volumes:docker-compose.yaml file specifies the three web services.
2, start the application
Create a webapp directory and copy the file to the docker-compose.yaml webapp directory, start the application using the docker-compose.docker-compose up -d
3, service access
Web1 access through a browser, web2, web3 service:
http://127.0.0.1:6061
http://127.0.0.1:6062
http://127.0.0.1:6063