-
Notifications
You must be signed in to change notification settings - Fork 284
Open
Labels
community_newNew idea raised by a community contributorNew idea raised by a community contributor
Description
It will be nice to have option for grouping containers in single docker compose.
For example
compose structure:
📝 compose.yaml ### compose with networks, databases, redis... etc. aka main compose
📝 compose.override.yaml ### depends_on, profiles, labels... etc
📝.env
📁 1-project
--- 📝 compose.yaml ### compose with work loads
--- 📝.env
📁 2-project
--- 📝 compose.yaml
--- 📝.envrun examples:
docker compose -f ./compose.yaml -f ./1-project/compose.yaml -f ./2-project/compose.yaml up -d # file merge
# OR
docker compose --profile 1-project up -d # merge with 'includes' in main compose file Any way docker desktop ui shows single root group named docker-compose or name field in main compose file, becouse of merge strategy:
- docker-compose
--- main-service1
--- main-service2
--- project1-service1
--- project2-service1Is it possible to change UI grouping for example by service label (f):
services:
project1-service1:
deploy:
label:
com.docker.compose.project-displayname: "project1"- docker-compose
--- main-service1
--- main-service2
- project1
--- project1-service1
- project2
--- project2-service1
### this structure same as running multiple `docker compose` with different files, but `depends_on` across projects will couse errorsThis feature will improove UX with partial start/stop/remove/log-monitoring and keep depends_on option, becouse it will be still single compose file
Metadata
Metadata
Assignees
Labels
community_newNew idea raised by a community contributorNew idea raised by a community contributor