docker_compose.yaml 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362
  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. ### Use Dry Run mode to test your command
  93. Use `--dry-run` flag to test a command without changing your application stack state.
  94. Dry Run mode shows you all the steps Compose applies when executing a command, for example:
  95. ```console
  96. $ docker compose --dry-run up --build -d
  97. [+] Pulling 1/1
  98. ✔ DRY-RUN MODE - db Pulled 0.9s
  99. [+] Running 10/8
  100. ✔ DRY-RUN MODE - build service backend 0.0s
  101. ✔ DRY-RUN MODE - ==> ==> writing image dryRun-754a08ddf8bcb1cf22f310f09206dd783d42f7dd 0.0s
  102. ✔ DRY-RUN MODE - ==> ==> naming to nginx-golang-mysql-backend 0.0s
  103. ✔ DRY-RUN MODE - Network nginx-golang-mysql_default Created 0.0s
  104. ✔ DRY-RUN MODE - Container nginx-golang-mysql-db-1 Created 0.0s
  105. ✔ DRY-RUN MODE - Container nginx-golang-mysql-backend-1 Created 0.0s
  106. ✔ DRY-RUN MODE - Container nginx-golang-mysql-proxy-1 Created 0.0s
  107. ✔ DRY-RUN MODE - Container nginx-golang-mysql-db-1 Healthy 0.5s
  108. ✔ DRY-RUN MODE - Container nginx-golang-mysql-backend-1 Started 0.0s
  109. ✔ DRY-RUN MODE - Container nginx-golang-mysql-proxy-1 Started Started
  110. ```
  111. From the example above, you can see that the first step is to pull the image defined by `db` service, then build the `backend` service.
  112. Next, the containers are created. The `db` service is started, and the `backend` and `proxy` wait until the `db` service is healthy before starting.
  113. Dry Run mode does not currently work with all commands. In particular, you cannot use Dry Run mode with a command that doesn't change the state of a Compose stack
  114. such as `ps`, `ls`, `logs` for example.
  115. Here the list of commands supporting `--dry-run` flag:
  116. * build
  117. * cp
  118. * create
  119. * down
  120. * exec
  121. * kill
  122. * pause
  123. * pull
  124. * push
  125. * remove
  126. * restart
  127. * run
  128. * start
  129. * stop
  130. * unpause
  131. * up
  132. usage: docker compose
  133. pname: docker
  134. plink: docker.yaml
  135. cname:
  136. - docker compose build
  137. - docker compose config
  138. - docker compose cp
  139. - docker compose create
  140. - docker compose down
  141. - docker compose events
  142. - docker compose exec
  143. - docker compose images
  144. - docker compose kill
  145. - docker compose logs
  146. - docker compose ls
  147. - docker compose pause
  148. - docker compose port
  149. - docker compose ps
  150. - docker compose pull
  151. - docker compose push
  152. - docker compose restart
  153. - docker compose rm
  154. - docker compose run
  155. - docker compose start
  156. - docker compose stop
  157. - docker compose top
  158. - docker compose unpause
  159. - docker compose up
  160. - docker compose version
  161. clink:
  162. - docker_compose_build.yaml
  163. - docker_compose_config.yaml
  164. - docker_compose_cp.yaml
  165. - docker_compose_create.yaml
  166. - docker_compose_down.yaml
  167. - docker_compose_events.yaml
  168. - docker_compose_exec.yaml
  169. - docker_compose_images.yaml
  170. - docker_compose_kill.yaml
  171. - docker_compose_logs.yaml
  172. - docker_compose_ls.yaml
  173. - docker_compose_pause.yaml
  174. - docker_compose_port.yaml
  175. - docker_compose_ps.yaml
  176. - docker_compose_pull.yaml
  177. - docker_compose_push.yaml
  178. - docker_compose_restart.yaml
  179. - docker_compose_rm.yaml
  180. - docker_compose_run.yaml
  181. - docker_compose_start.yaml
  182. - docker_compose_stop.yaml
  183. - docker_compose_top.yaml
  184. - docker_compose_unpause.yaml
  185. - docker_compose_up.yaml
  186. - docker_compose_version.yaml
  187. options:
  188. - option: ansi
  189. value_type: string
  190. default_value: auto
  191. description: |
  192. Control when to print ANSI control characters ("never"|"always"|"auto")
  193. deprecated: false
  194. hidden: false
  195. experimental: false
  196. experimentalcli: false
  197. kubernetes: false
  198. swarm: false
  199. - option: compatibility
  200. value_type: bool
  201. default_value: "false"
  202. description: Run compose in backward compatibility mode
  203. deprecated: false
  204. hidden: false
  205. experimental: false
  206. experimentalcli: false
  207. kubernetes: false
  208. swarm: false
  209. - option: dry-run
  210. value_type: bool
  211. default_value: "false"
  212. description: Execute command in dry run mode
  213. deprecated: false
  214. hidden: false
  215. experimental: false
  216. experimentalcli: false
  217. kubernetes: false
  218. swarm: false
  219. - option: env-file
  220. value_type: stringArray
  221. default_value: '[]'
  222. description: Specify an alternate environment file.
  223. deprecated: false
  224. hidden: false
  225. experimental: false
  226. experimentalcli: false
  227. kubernetes: false
  228. swarm: false
  229. - option: file
  230. shorthand: f
  231. value_type: stringArray
  232. default_value: '[]'
  233. description: Compose configuration files
  234. deprecated: false
  235. hidden: false
  236. experimental: false
  237. experimentalcli: false
  238. kubernetes: false
  239. swarm: false
  240. - option: no-ansi
  241. value_type: bool
  242. default_value: "false"
  243. description: Do not print ANSI control characters (DEPRECATED)
  244. deprecated: false
  245. hidden: true
  246. experimental: false
  247. experimentalcli: false
  248. kubernetes: false
  249. swarm: false
  250. - option: parallel
  251. value_type: int
  252. default_value: "-1"
  253. description: Control max parallelism, -1 for unlimited
  254. deprecated: false
  255. hidden: false
  256. experimental: false
  257. experimentalcli: false
  258. kubernetes: false
  259. swarm: false
  260. - option: profile
  261. value_type: stringArray
  262. default_value: '[]'
  263. description: Specify a profile to enable
  264. deprecated: false
  265. hidden: false
  266. experimental: false
  267. experimentalcli: false
  268. kubernetes: false
  269. swarm: false
  270. - option: project-directory
  271. value_type: string
  272. description: |-
  273. Specify an alternate working directory
  274. (default: the path of the, first specified, Compose file)
  275. deprecated: false
  276. hidden: false
  277. experimental: false
  278. experimentalcli: false
  279. kubernetes: false
  280. swarm: false
  281. - option: project-name
  282. shorthand: p
  283. value_type: string
  284. description: Project name
  285. deprecated: false
  286. hidden: false
  287. experimental: false
  288. experimentalcli: false
  289. kubernetes: false
  290. swarm: false
  291. - option: verbose
  292. value_type: bool
  293. default_value: "false"
  294. description: Show more output
  295. deprecated: false
  296. hidden: true
  297. experimental: false
  298. experimentalcli: false
  299. kubernetes: false
  300. swarm: false
  301. - option: version
  302. shorthand: v
  303. value_type: bool
  304. default_value: "false"
  305. description: Show the Docker Compose version information
  306. deprecated: false
  307. hidden: true
  308. experimental: false
  309. experimentalcli: false
  310. kubernetes: false
  311. swarm: false
  312. - option: workdir
  313. value_type: string
  314. description: |-
  315. DEPRECATED! USE --project-directory INSTEAD.
  316. Specify an alternate working directory
  317. (default: the path of the, first specified, Compose file)
  318. deprecated: false
  319. hidden: true
  320. experimental: false
  321. experimentalcli: false
  322. kubernetes: false
  323. swarm: false
  324. deprecated: false
  325. experimental: false
  326. experimentalcli: false
  327. kubernetes: false
  328. swarm: false