Nested docker-compose.yml

[jasonalsing]

i have a single project 'docker' with directory /home/user/docker and docker-compose.yml within this directory. also in this directory are additional sub-directories for container configs, so I have /home/user/docker/caddy, etc. I run docker-compose-ui with /home/user/docker mounted as per the directions and "working_dir" set to /home/user. This previously worked, when I refresh projects I get "docker" and all the containers and able to see the docker-compose.yml just fine.

Now one day i installed a container (node-red) with a mount to /home/user/docker/node-red for config like the rest, but for whatever reason deep in this directory there is a docker-compose.yml. I think like a sample file or something. But this caused docker-compose-ui to find and only use that node-red version of docker-compose.yml instead of the higher level one in /home/user/docker.

Of course I don't need this node-red version so I rename it and docker-compose-ui now uses the proper docker-compose.yml.

Not sure if this is by design? or a bug.