In this section, there are two common use cases for multiple Compose files: changing aĬompose app for different environments, and running administrative tasksĪgainst a Compose app. Tracking which fragment of a service is relative to which path is difficult andĬonfusing, so to keep paths easier to understand, all paths must be defined Override files can contain small fragments of configuration. This is required because override files need not be validĬompose files. When you use multiple configuration files, you must make sure all paths in theįiles are relative to the base Compose file (the first Compose file specified See theĭocker compose command reference for more information The order they’re specified on the command line.

To use multiple override files, or an override file with a different name, youĬan use the -f option to specify the list of files. If a service is defined in both files, Compose merges the configurations using The override file, as its name implies, canĬontain configuration overrides for existing services or entirely new By convention, the docker-compose.ymlĬontains your base configuration. Understanding multiple Compose filesīy default, Compose reads two files, a docker-compose.yml and an optionalĭ file. Using multiple Compose files lets you to customize a Compose applicationįor different environments or different workflows. Extend individual services with the extends field.For more information, see the Evolution of ComposeĬompose supports two methods of sharing common configuration: Make sure you switch to Compose V2 with the docker compose CLI plugin or by activating the Use Docker Compose V2 setting in Docker Desktop. Share Compose configurations between files and projectsįrom the end of June 2023 Compose V1 won’t be supported anymore and will be removed from all Docker Desktop versions.

How to convert a file into extra base