docker_compose.yaml 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317
  1. command: docker compose
  2. short: Docker Compose
  3. long: |-
  4. You can use compose subcommand, `docker compose [-f <arg>...] [options] [COMMAND] [ARGS...]`, to build and manage
  5. multiple services in Docker containers.
  6. ### Use `-f` to specify the name and path of one or more Compose files
  7. Use the `-f` flag to specify the location of a Compose configuration file.
  8. #### Specifying multiple Compose files
  9. You can supply multiple `-f` configuration files. When you supply multiple files, Compose combines them into a single
  10. configuration. Compose builds the configuration in the order you supply the files. Subsequent files override and add
  11. to their predecessors.
  12. For example, consider this command line:
  13. ```console
  14. $ docker compose -f docker-compose.yml -f docker-compose.admin.yml run backup_db
  15. ```
  16. The `docker-compose.yml` file might specify a `webapp` service.
  17. ```yaml
  18. services:
  19. webapp:
  20. image: examples/web
  21. ports:
  22. - "8000:8000"
  23. volumes:
  24. - "/data"
  25. ```
  26. If the `docker-compose.admin.yml` also specifies this same service, any matching fields override the previous file.
  27. New values, add to the `webapp` service configuration.
  28. ```yaml
  29. services:
  30. webapp:
  31. build: .
  32. environment:
  33. - DEBUG=1
  34. ```
  35. When you use multiple Compose files, all paths in the files are relative to the first configuration file specified
  36. with `-f`. You can use the `--project-directory` option to override this base path.
  37. Use a `-f` with `-` (dash) as the filename to read the configuration from stdin. When stdin is used all paths in the
  38. configuration are relative to the current working directory.
  39. The `-f` flag is optional. If you don’t provide this flag on the command line, Compose traverses the working directory
  40. and its parent directories looking for a `compose.yaml` or `docker-compose.yaml` file.
  41. #### Specifying a path to a single Compose file
  42. You can use the `-f` flag to specify a path to a Compose file that is not located in the current directory, either
  43. from the command line or by setting up a `COMPOSE_FILE` environment variable in your shell or in an environment file.
  44. For an example of using the `-f` option at the command line, suppose you are running the Compose Rails sample, and
  45. have a `compose.yaml` file in a directory called `sandbox/rails`. You can use a command like `docker compose pull` to
  46. get the postgres image for the db service from anywhere by using the `-f` flag as follows:
  47. ```console
  48. $ docker compose -f ~/sandbox/rails/compose.yaml pull db
  49. ```
  50. ### Use `-p` to specify a project name
  51. Each configuration has a project name. Compose sets the project name using
  52. the following mechanisms, in order of precedence:
  53. - The `-p` command line flag
  54. - The `COMPOSE_PROJECT_NAME` environment variable
  55. - The top level `name:` variable from the config file (or the last `name:`
  56. from a series of config files specified using `-f`)
  57. - The `basename` of the project directory containing the config file (or
  58. containing the first config file specified using `-f`)
  59. - The `basename` of the current directory if no config file is specified
  60. Project names must contain only lowercase letters, decimal digits, dashes,
  61. and underscores, and must begin with a lowercase letter or decimal digit. If
  62. the `basename` of the project directory or current directory violates this
  63. constraint, you must use one of the other mechanisms.
  64. ```console
  65. $ docker compose -p my_project ps -a
  66. NAME SERVICE STATUS PORTS
  67. my_project_demo_1 demo running
  68. $ docker compose -p my_project logs
  69. demo_1 | PING localhost (127.0.0.1): 56 data bytes
  70. demo_1 | 64 bytes from 127.0.0.1: seq=0 ttl=64 time=0.095 ms
  71. ```
  72. ### Use profiles to enable optional services
  73. Use `--profile` to specify one or more active profiles
  74. Calling `docker compose --profile frontend up` will start the services with the profile `frontend` and services
  75. without any specified profiles.
  76. You can also enable multiple profiles, e.g. with `docker compose --profile frontend --profile debug up` the profiles `frontend` and `debug` will be enabled.
  77. Profiles can also be set by `COMPOSE_PROFILES` environment variable.
  78. ### Configuring parallelism
  79. Use `--parallel` to specify the maximum level of parallelism for concurrent engine calls.
  80. Calling `docker compose --parallel 1 pull` will pull the pullable images defined in the Compose file
  81. one at a time. This can also be used to control build concurrency.
  82. Parallelism can also be set by the `COMPOSE_PARALLEL_LIMIT` environment variable.
  83. ### Set up environment variables
  84. You can set environment variables for various docker compose options, including the `-f`, `-p` and `--profiles` flags.
  85. Setting the `COMPOSE_FILE` environment variable is equivalent to passing the `-f` flag,
  86. `COMPOSE_PROJECT_NAME` environment variable does the same as the `-p` flag,
  87. `COMPOSE_PROFILES` environment variable is equivalent to the `--profiles` flag
  88. and `COMPOSE_PARALLEL_LIMIT` does the same as the `--parallel` flag.
  89. If flags are explicitly set on the command line, the associated environment variable is ignored.
  90. Setting the `COMPOSE_IGNORE_ORPHANS` environment variable to `true` will stop docker compose from detecting orphaned
  91. containers for the project.
  92. usage: docker compose
  93. pname: docker
  94. plink: docker.yaml
  95. cname:
  96. - docker compose build
  97. - docker compose config
  98. - docker compose cp
  99. - docker compose create
  100. - docker compose down
  101. - docker compose events
  102. - docker compose exec
  103. - docker compose images
  104. - docker compose kill
  105. - docker compose logs
  106. - docker compose ls
  107. - docker compose pause
  108. - docker compose port
  109. - docker compose ps
  110. - docker compose pull
  111. - docker compose push
  112. - docker compose restart
  113. - docker compose rm
  114. - docker compose run
  115. - docker compose start
  116. - docker compose stop
  117. - docker compose top
  118. - docker compose unpause
  119. - docker compose up
  120. - docker compose version
  121. clink:
  122. - docker_compose_build.yaml
  123. - docker_compose_config.yaml
  124. - docker_compose_cp.yaml
  125. - docker_compose_create.yaml
  126. - docker_compose_down.yaml
  127. - docker_compose_events.yaml
  128. - docker_compose_exec.yaml
  129. - docker_compose_images.yaml
  130. - docker_compose_kill.yaml
  131. - docker_compose_logs.yaml
  132. - docker_compose_ls.yaml
  133. - docker_compose_pause.yaml
  134. - docker_compose_port.yaml
  135. - docker_compose_ps.yaml
  136. - docker_compose_pull.yaml
  137. - docker_compose_push.yaml
  138. - docker_compose_restart.yaml
  139. - docker_compose_rm.yaml
  140. - docker_compose_run.yaml
  141. - docker_compose_start.yaml
  142. - docker_compose_stop.yaml
  143. - docker_compose_top.yaml
  144. - docker_compose_unpause.yaml
  145. - docker_compose_up.yaml
  146. - docker_compose_version.yaml
  147. options:
  148. - option: ansi
  149. value_type: string
  150. default_value: auto
  151. description: |
  152. Control when to print ANSI control characters ("never"|"always"|"auto")
  153. deprecated: false
  154. hidden: false
  155. experimental: false
  156. experimentalcli: false
  157. kubernetes: false
  158. swarm: false
  159. - option: compatibility
  160. value_type: bool
  161. default_value: "false"
  162. description: Run compose in backward compatibility mode
  163. deprecated: false
  164. hidden: false
  165. experimental: false
  166. experimentalcli: false
  167. kubernetes: false
  168. swarm: false
  169. - option: dry-run
  170. value_type: bool
  171. default_value: "false"
  172. description: Execute command in dry run mode
  173. deprecated: false
  174. hidden: true
  175. experimental: false
  176. experimentalcli: false
  177. kubernetes: false
  178. swarm: false
  179. - option: env-file
  180. value_type: stringArray
  181. default_value: '[]'
  182. description: Specify an alternate environment file.
  183. deprecated: false
  184. hidden: false
  185. experimental: false
  186. experimentalcli: false
  187. kubernetes: false
  188. swarm: false
  189. - option: file
  190. shorthand: f
  191. value_type: stringArray
  192. default_value: '[]'
  193. description: Compose configuration files
  194. deprecated: false
  195. hidden: false
  196. experimental: false
  197. experimentalcli: false
  198. kubernetes: false
  199. swarm: false
  200. - option: no-ansi
  201. value_type: bool
  202. default_value: "false"
  203. description: Do not print ANSI control characters (DEPRECATED)
  204. deprecated: false
  205. hidden: true
  206. experimental: false
  207. experimentalcli: false
  208. kubernetes: false
  209. swarm: false
  210. - option: parallel
  211. value_type: int
  212. default_value: "-1"
  213. description: Control max parallelism, -1 for unlimited
  214. deprecated: false
  215. hidden: false
  216. experimental: false
  217. experimentalcli: false
  218. kubernetes: false
  219. swarm: false
  220. - option: profile
  221. value_type: stringArray
  222. default_value: '[]'
  223. description: Specify a profile to enable
  224. deprecated: false
  225. hidden: false
  226. experimental: false
  227. experimentalcli: false
  228. kubernetes: false
  229. swarm: false
  230. - option: project-directory
  231. value_type: string
  232. description: |-
  233. Specify an alternate working directory
  234. (default: the path of the, first specified, Compose file)
  235. deprecated: false
  236. hidden: false
  237. experimental: false
  238. experimentalcli: false
  239. kubernetes: false
  240. swarm: false
  241. - option: project-name
  242. shorthand: p
  243. value_type: string
  244. description: Project name
  245. deprecated: false
  246. hidden: false
  247. experimental: false
  248. experimentalcli: false
  249. kubernetes: false
  250. swarm: false
  251. - option: verbose
  252. value_type: bool
  253. default_value: "false"
  254. description: Show more output
  255. deprecated: false
  256. hidden: true
  257. experimental: false
  258. experimentalcli: false
  259. kubernetes: false
  260. swarm: false
  261. - option: version
  262. shorthand: v
  263. value_type: bool
  264. default_value: "false"
  265. description: Show the Docker Compose version information
  266. deprecated: false
  267. hidden: true
  268. experimental: false
  269. experimentalcli: false
  270. kubernetes: false
  271. swarm: false
  272. - option: workdir
  273. value_type: string
  274. description: |-
  275. DEPRECATED! USE --project-directory INSTEAD.
  276. Specify an alternate working directory
  277. (default: the path of the, first specified, Compose file)
  278. deprecated: false
  279. hidden: true
  280. experimental: false
  281. experimentalcli: false
  282. kubernetes: false
  283. swarm: false
  284. deprecated: false
  285. experimental: false
  286. experimentalcli: false
  287. kubernetes: false
  288. swarm: false