[Bug]: Compose File Discovery

[lordraiden]

Version

5.0.2

Unraid Version

7.2.3

Bug Description

Compose File Discovery - Automatically detects all four standard compose file names (compose.yaml, docker-compose.yaml, compose.yml, docker-compose.yml).

Regarding this feature when I try to import this project, compose manager creates a compose.yaml file that wasn't there before.

at the same time in the compose manager path it creates this file that I guess it should be docker-compose.override.yml

The way to fix it is renaming the override but I guess this should be done automatically by compose manager

On the other hand does compose manager honor the labels like?
net.unraid.docker.managed: "composeman"
net.unraid.docker.shell: "sh"
net.unraid.docker.icon: "https://raw.githubusercontent.com/falcosecurity/falcosidekick-ui/master/public/logo.png"
net.unraid.docker.webui: "https://${falcosidekick_ui_name}.${mydomain}/"

Expected Behavior

It should work

Steps to Reproduce

See bug

Relevant Logs

Compose

Additional Context

No response

[mstrhakr]

5.0.2 is the compose version I need to add a label to that so its more obvious (or move/remove it). What is your plugin version, I just fixed this #91. Are you on the latest plugin version? Plugin version is a date, latest stable is v2026.04.10. This can be checked on the plugins tab.

[lordraiden]

I'm using 2026.04.10 v5.0.2

[mstrhakr]

Testing with 2026.04.10, I'm not able to reproduce this issue. Please confirm you've cleaned up from the previous failure (removed the extra compose.yaml file) as the file search has a preference for compose.yaml, compose.yml, docker-compose.yaml, and then docker-compose.yml in that order. If that empty compose.yaml file still exist, then the scanner will find it first. Please fix that, enable debug logging, then try again. If it still fails post the logs and I can look again.

[mstrhakr]

On the other hand does compose manager honor the labels like?
net.unraid.docker.managed: "composeman"
net.unraid.docker.shell: "sh"
net.unraid.docker.icon: "https://raw.githubusercontent.com/falcosecurity/falcosidekick-ui/master/public/logo.png"
net.unraid.docker.webui: "https://${falcosidekick_ui_name}.${mydomain}/"

If these are in your compose file, it should be applied to the running stack, which should be all that matters. So long as you don't have placeholders/empty strings set in the override file. I will have to double check how the generation goes and if it would make placeholders or if like I assume, it would only do this if you edit something in that section (like add an icon via the UI) and save. I'll look into this here shortly.

[lordraiden]

Testing with 2026.04.10, I'm not able to reproduce this issue. Please confirm you've cleaned up from the previous failure (removed the extra compose.yaml file) as the file search has a preference for compose.yaml, compose.yml, docker-compose.yaml, and then docker-compose.yml in that order. If that empty compose.yaml file still exist, then the scanner will find it first. Please fix that, enable debug logging, then try again. If it still fails post the logs and I can look again.

I cleaned up everything and it worked fine this time, maybe I have a previous compose.yml file or something that confused compose manager.

Regarding webui labels tab apparently they are working fine too. But this one net.unraid.docker.managed: "composeman" i don't know because I don't remember what it does