Incorrect inactive status for a running stack (librechat)

[vihu]

⚠️ Please verify that this bug has NOT been reported before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

I setup librechat using their instructions. Notably there's a difference when using their npm run start:deployed command as it deploys a separate deploy-compose.yml file and uses the regular docker-compose.yml as a template.

On dockge this stack seemingly gets incorrectly reported as "inactive" despite all the containers running (as seen in the screenshot below):

👟 Reproduction steps

Deploy librechat using their instructions here: https://www.librechat.ai/docs/remote/docker_linux all the way upto the npm run start:deployed command.

👀 Expected behavior

I expect that since the containers are actually running correctly, dockge should report the stack as active.

😓 Actual Behavior

dockge reports the stack as inactive despite all the containers running

Dockge Version

1.4.2

💻 Operating System and Arch

Ubuntu 20.04 x64

🌐 Browser

Firefox

🐋 Docker Version

Docker version 27.1.2, build d01f264

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[LeonardoCT]

i can confirm, that i'm facing the same issue:

I'm running on TrueNAS Scale (TrueNAS-SCALE-ElectricEel-BETA)

All the components in the stack work as expected

[DomiiBunn]

Without looking into the provided stacks.

If they have either name in the docker compose as a root value or COMPOSE_PROJECT_NAME as an env value docker compose will set the stack name to it. This will cause issues with dockge as it expects the stack name to be the same as it's own defined name. If they are different you get the inactive bug

Something that could be solved updating the parser