Stack with explicit name is not recognized #232

New issue

Open

opened 2026-02-20 13:12:25 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 13:12:25 -05:00

Owner

Originally created by @Fumblesneeze on GitHub (Nov 5, 2025).

⚠️ 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

docker compose lets you explicitly set the name of the stack by adding a top level name field like:

name: my-stack
services:
...

however this is not recognized by dockge and it displays the stack as inactive, even though the stack and all containers are up and running, and the containers in the stack are even recognized by dockge.

👟 Reproduction steps

add

name: my-stack

to the top level of a docker compose file

👀 Expected behavior

dockge should either display the stack with the name that was explicitly set up, or at least recognize the changed stack name when determining the state of the stack.

😓 Actual Behavior

dockge shows such a stack as inactive.

Dockge Version

Version: 1.5.0

💻 Operating System and Arch

Docker

🌐 Browser

Edge

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

Originally created by @Fumblesneeze on GitHub (Nov 5, 2025). ### ⚠️ Please verify that this bug has NOT been reported before. - [x] I checked and didn't find similar issue ### 🛡️ Security Policy - [x] I agree to have read this project [Security Policy](https://github.com/louislam/dockge/security/policy) ### Description docker compose lets you explicitly set the name of the stack by adding a top level name field like: ``` name: my-stack services: ... ``` however this is not recognized by dockge and it displays the stack as inactive, even though the stack and all containers are up and running, and the containers in the stack are even recognized by dockge. ### 👟 Reproduction steps add ``` name: my-stack ``` to the top level of a docker compose file ### 👀 Expected behavior dockge should either display the stack with the name that was explicitly set up, or at least recognize the changed stack name when determining the state of the stack. ### 😓 Actual Behavior dockge shows such a stack as inactive. ### Dockge Version Version: 1.5.0 ### 💻 Operating System and Arch Docker ### 🌐 Browser Edge ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output ```shell ```

deekerman added the

bug

label

2026-02-20 13:12:25 -05:00

deekerman commented

2026-02-20 13:12:26 -05:00

Author

Owner

@Tux7486 commented on GitHub (Feb 9, 2026):

I can see one stack with the name that is set in the compose file and another one with the folder name.
First tought my containers are messed up but I do think it has to do with this name.

@Tux7486 commented on GitHub (Feb 9, 2026): I can see one stack with the name that is set in the compose file and another one with the folder name. First tought my containers are messed up but I do think it has to do with this name.