[Bug]: cant start complex project (akvorado)

[journeym]

Version

latest

Unraid Version

7.3.1

Bug Description

I can perfectly use docker compose on the same host to get akvorado running, but when im trying to use gui i run into all sorts of problems, for example if i just copy the dir with environment into default project dir, it's not even showing me the stack.
If i try to add it manually, i can, if i specify the custom eml path as well as custom .env path, but then he cant get the base right, and project fails to copy files inside containers.

Directory structure in this project is:
root@amn:/boot/config/plugins/compose.manager/projects/akvorado# tree -a
.
├── .env
├── config
│ ├── akvorado.yaml
│ ├── console.yaml
│ ├── demo-1.yaml
│ ├── demo-2.yaml
│ ├── demo-3.yaml
│ ├── demo-4.yaml
│ ├── demo-bmp.yaml
│ ├── demo-flows.yaml
│ ├── inlet.yaml
│ └── outlet.yaml
└── docker
├── Dockerfile
├── Dockerfile.dev
├── Dockerfile.dev.dockerignore
├── Dockerfile.dockerignore
├── Dockerfile.ipinfo-geoipupdate
├── Dockerfile.ipinfo-geoipupdate.dockerignore
├── Dockerfile.nix
├── clickhouse
│ ├── cluster-1.xml
│ ├── cluster-2.xml
│ ├── cluster-3.xml
│ ├── cluster-4.xml
│ ├── cluster-dev.xml
│ ├── cluster.xml
│ ├── dev.xml
│ ├── keeper-cluster-1.xml
│ ├── keeper-cluster-2.xml
│ ├── keeper-cluster-3.xml
│ ├── keeper-cluster.xml
│ ├── keeper.xml
│ ├── observability.xml
│ └── server.xml
├── config.alloy
├── docker-compose-clickhouse-cluster.yml
├── docker-compose-demo.yml
├── docker-compose-dev.yml
├── docker-compose-grafana.yml
├── docker-compose-ipinfo.yml
├── docker-compose-local.yml
├── docker-compose-loki.yml
├── docker-compose-maxmind.yml
├── docker-compose-prometheus.yml
├── docker-compose-tls.yml
├── docker-compose.yml
├── grafana
│ ├── dashboards
│ │ └── akvorado
│ │ ├── inlet.json
│ │ └── troubleshooting.json
│ ├── grafana.ini
│ └── provisioning
│ ├── dashboards
│ │ └── akvorado.yaml
│ └── datasources
│ └── akvorado.yaml
├── ipinfo-geoipupdate.sh
├── loki.yaml
├── prometheus.yml
├── traefik-forward-auth.yaml
├── vector.tests.yaml
├── vector.yaml
└── versions.yml

Expected Behavior

same beahaivior as docker compose up in the project dir

Steps to Reproduce

mkdir akvorado
cd akvorado
curl -sL https://github.com/akvorado/akvorado/releases/latest/download/docker-compose-quickstart.tar.gz | tar zxvf -
docker compose up --wait

Watch its working

stop it and try to add it into GUI

Relevant Logs

Compose

Additional Context

No response

[mstrhakr]

In the advanced settings for the stack (on the current version, it will be in the Source tab in the next release) you need to set compose file discovery to default mode.

Current Version - Check the box to change modes:

Next Version - Click "Use Default Discovery" to change modes:

[journeym]

Did you try it? It doesn't change anything. Either it starts but without geoip container (because it fails in Copy stage on wrong base), or it doesn't detect it, and can't start at all. I tried different options throughout the week, and this one also

…

On Fri, Sep 4, 2026, 03:02 Nick Szittai ***@***.***> wrote: *mstrhakr* left a comment (mstrhakr/compose_plugin#149) <#149 (comment)> In the advanced settings for the stack (on the current version, it will be in the Source tab in the next release) you need to set compose file discovery to default mode. Current Version - Check the box to change modes: Image: Image (view on web) <https://github.com/user-attachments/assets/0cce9ebd-04ef-40a0-a73a-84f134bf567c> Next Version - Click "Use Default Discovery" to change modes: Image: Image (view on web) <https://github.com/user-attachments/assets/0f0f2e08-0dfd-49ad-ab87-56fb30c9b8bc> — Reply to this email directly, view it on GitHub <#149?email_source=notifications&email_token=AB3GO5XZDVERQDY2BYBVBCT5NIBARA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNJTGM3TCMBQHAYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5533710080>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3GO5XQPAWTZWK4GIXVUXT5NIBARAVCNFSNUABGKJSXA33TNF2G64TZHMYTCNBWHA2DANBRGY5US43TOVSTWNJTGQYTKNJRHA2DLILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AB3GO5V36C3ERH7D3OGN7U35NIBARA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNJTGM3TCMBQHAYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AB3GO5QITEH7SPOBEESM6KT5NIBARA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKNJTGM3TCMBQHAYKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[mstrhakr]

I hadn't, but after trying it I'll be looking into this to try to get this working for you. Its definitely a strange compose setup but it works normally so I feel like it should just work here.

[journeym]

it works if i place the project .env file in the root of the configured Compose Project Directory.
structure is unchanged, but if i create subdirectory under Compose Project Directory and move the project there it's unable to see it.
It seems gui is looking for yml files in subdirectories, not in sub\sub direcroties.

Structure when it's working:
`root@amn:/mnt/user/data/compose# tree -a
.
├── .env
├── akvorado.svg
├── config
│ ├── akvorado.yaml
│ ├── console.yaml
│ ├── demo-1.yaml
│ ├── demo-2.yaml
│ ├── demo-3.yaml
│ ├── demo-4.yaml
│ ├── demo-bmp.yaml
│ ├── demo-flows.yaml
│ ├── inlet.yaml
│ ├── name
│ ├── outlet.yaml
│ └── project_name
├── docker
│ ├── .compose_follow.pid
│ ├── Dockerfile
│ ├── Dockerfile.dev
│ ├── Dockerfile.dev.dockerignore
│ ├── Dockerfile.dockerignore
│ ├── Dockerfile.ipinfo-geoipupdate
│ ├── Dockerfile.ipinfo-geoipupdate.dockerignore
│ ├── Dockerfile.nix
│ ├── autostart
│ ├── clickhouse
│ │ ├── cluster-1.xml
│ │ ├── cluster-2.xml
│ │ ├── cluster-3.xml
│ │ ├── cluster-4.xml
│ │ ├── cluster-dev.xml
│ │ ├── cluster.xml
│ │ ├── dev.xml
│ │ ├── keeper-cluster-1.xml
│ │ ├── keeper-cluster-2.xml
│ │ ├── keeper-cluster-3.xml
│ │ ├── keeper-cluster.xml
│ │ ├── keeper.xml
│ │ ├── observability.xml
│ │ └── server.xml
│ ├── config.alloy
│ ├── docker-compose-clickhouse-cluster.yml
│ ├── docker-compose-demo.yml
│ ├── docker-compose-dev.yml
│ ├── docker-compose-grafana.yml
│ ├── docker-compose-ipinfo.yml
│ ├── docker-compose-local.yml
│ ├── docker-compose-loki.yml
│ ├── docker-compose-maxmind.yml
│ ├── docker-compose-prometheus.yml
│ ├── docker-compose-tls.yml
│ ├── docker-compose.yml
│ ├── extra_compose_files
│ ├── grafana
│ │ ├── dashboards
│ │ │ └── akvorado
│ │ │ ├── inlet.json
│ │ │ └── troubleshooting.json
│ │ ├── grafana.ini
│ │ └── provisioning
│ │ ├── dashboards
│ │ │ └── akvorado.yaml
│ │ └── datasources
│ │ └── akvorado.yaml
│ ├── has_build
│ ├── icon_url
│ ├── ipinfo-geoipupdate.sh
│ ├── last_cmd.log
│ ├── last_result.json
│ ├── loki.yaml
│ ├── name
│ ├── project_name
│ ├── prometheus.yml
│ ├── started_at
│ ├── traefik-forward-auth.yaml
│ ├── vector.tests.yaml
│ ├── vector.yaml
│ ├── versions.yml
│ └── webui_url
├── name
└── project_name

10 directories, 72 files`

[mstrhakr]

Try this on the latest beta and let me know.

[journeym]

It works with subfolder now, but still there is a problem with logic somewhere. It doesnt create geoip container, though docker compose up command creates this container. I didnt find any errors in a log regarding this.
Im also unable to select it to start form a list now, there is no list of possible docker containers, as it was earlier

[journeym]

docker compose up -d from the same folder

[journeym]

For example, when the project is in the root of configured project directory, i can select geoip container (ipinfo) manually and it starts.

So please either add this additional config section for subfolders, or somehow get to the bottom of why it isnt starting in the first place. Wild guess would be the same error i got earlier with this container when configured manually. Wrong base when copying the ipinfo-geoipupdate.sh inside the geoip container. But im not sure cause this error isnt present in the log currently

[journeym]

I cant update though even if it's in the root of projects folder, the same error with base

[mstrhakr]

Please check again in the latest beta, this should be solved now. I'll releasing this on the stable branch soon either way.