Open HernandoR opened 1 month ago
Describe the bug By the docker compose spec, each included files should be treated as individual project. Meaning that
suggesting a structure as
./include/ ├── docker-compose.yaml ├── extend │ └── docker-compose.extend.yaml └── extend2 └── docker-compose.extend2.yaml
where as each extended docker-compose try to map ./config, Calling docker compose at include
./config
Expected behavior
service in extend map extend/config; extend2 map extend2/config
extend
extend/config
extend2
extend2/config
Actual behavior
all service mapping include/config
include/config
Output
$ podman-compose version podman-compose version 1.0.7 podman version 4.3.1 podman --version podman version 4.3.1
Additional context
It is not a run time problem, but an designing inconsistance.
Related document Compose spec docker-compose/include
Describe the bug By the docker compose spec, each included files should be treated as individual project. Meaning that
suggesting a structure as
where as each extended docker-compose try to map
./config
, Calling docker compose at includeExpected behavior
service in
extend
mapextend/config
;extend2
mapextend2/config
Actual behavior
all service mapping
include/config
Output
Additional context
It is not a run time problem, but an designing inconsistance.