[Bug] Created stack in dockge, but dockge says the stack isn't managed by dockge

[anthonysmillie]

So I've just created a stack in dockge, got everything setup similar to how I used to run it (decided to recreate all of my config rather than import it) but now when I deploy it says it's not managed by dockge, despite the fact that I wrote and deployed it using dockge exclusively:

If I go to the inactive one it shows the running containers but I can't stop them:

[anthonysmillie]

To update here, this happens when deploying a stack with capital letters in the name. Dockge will let you create the stack, but once it's running and to show its status it looks for lower case letters only, thus the discrepancy.

Dockge needs to either not allow the creation of stacks with capital letters, or it needs to search for the stack name as-is, whether it's upper case or lower case, to update and display the status correctly.

[anthonysmillie]

Quick workaround for now, without having to delete and recreate (as you can't rename a stack), is to just rename the folder in ../stacks/ to lower case and then re-scan your stacks.

[louislam]

docker-compose will convert to lowercase internally. I think I have to restrict uppercase.

[ptmorris1]

docker-compose will convert to lowercase internally. I think I have to restrict uppercase.

Just another note, I had the same issue with a stack having a dash in the name, paperless-ngx, once the dash was removed no issues anymore. Thanks for the great work!

[louislam]

@ptmorris1

Are you sure about that? Because I have some stacks with dash without any problems.

[ptmorris1]

Interesting, I had recreated the stack half a dozen times before removing the dash and finally having that work. I am on a new install, never used a previous version before yesterday.

[markusglaetzner]

I get "This stack is not managed by dockge" too and the container shows this error messages:
2024-01-09T18:07:29+01:00 [GETSERVICESTATUSLIST] ERROR: Error: spawn docker ENOENT
at __node_internal_captureLargerStackTrace (node:internal/errors:496:5)
at __node_internal_errnoException (node:internal/errors:623:12)
at ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

[thewonderer73]

Same issue with first install of dockge. Could it be because I have Portainer running too? All containers were manually installed with a docker-compose.yaml file , not through portainer

[sanvit]

Same issue here with paperless-ngx. Others (even with those having - in their name seems to be fine.

Edit: the fix in #474 did it for me (changing the COMPOSE_PROJECT_NAME=paperless part in .env)