Trace: TypeError: composeStatus is not iterable

[gizmocuz]

Thank you for continuing Dockge!

After migrating to your image I encounter a issue that stops Dockge working.

Steps I took:

• removed the data folder
• adjusted the compose file (shown below)
• launched the container (without -d to see the output)
• registered an admin user

compose file:

services:
  dockge:
    image: cmcooper1980/dockge
    container_name: dockge
    restart: unless-stopped
    ports:
      - 5001:5001
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./data:/app/data
      - /opt:/opt
    environment:
      # Tell Dockge where to find the stacks
      - DOCKGE_STACKS_DIR=/opt
    networks:
      - backend
networks:
  backend:
    external: true

Dockge is installed in /opt/dockge

docker log output:

dockge  | Trace: TypeError: composeStatus is not iterable
dockge  |     at Function.isComposeExitClean (/app/backend/stack.ts:459:43)
dockge  |     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
dockge  |     at async Function.statusConvert (/app/backend/stack.ts:487:20)
dockge  |     at async Function.getStackList (/app/backend/stack.ts:389:29)
dockge  |     at async DockgeServer.sendStackList (/app/backend/dockge-server.ts:601:33)
dockge  |     at process.unexpectedErrorHandler (/app/backend/dockge-server.ts:89:21)
dockge  |     at process.emit (node:events:519:28)
dockge  |     at process.emit (/usr/local/lib/node_modules/tsx/dist/suppress-warnings.cjs:1:472)
dockge  |     at emitUnhandledRejection (node:internal/process/promises:252:13)
dockge  |     at throwUnhandledRejectionsMode (node:internal/process/promises:388:19)
dockge  |     at processPromiseRejections (node:internal/process/promises:475:17)
dockge  |     at process.processTicksAndRejections (node:internal/process/task_queues:106:32)
dockge  | If you keep encountering errors, please report to https://github.com/cmcooper1980/dockge

[gizmocuz]

Edit: Changing back the compose image to "louislam/dockge:latest" solves the issue, but is of course using an outdated version

[cmcooper1980]

I tried to spin an instance up from scratch (with the compose you provided, however, adjusting variables for my environment) to see if I'd have the same issue but I did not have any problems.

see video: https://youtu.be/SNiOKmjNp4k

maybe run compose down, prune your system, and spin back up...this worked in another discussion for that "composeStatus is not iterable" error

see closed discussion #22

[gizmocuz]

Thank you for the link to the previous issue. Should have seen that!

I executed all commands on 3 machines and all are working wonderful now!

I did notice on each machine that there was 1 volume deleted... could be that this was the cause!

Happy user here! Would be great if you could add an option to hide the 'Update All' button (could be very dangerous!), and an option to show a bullet if there was a update available on one of the dockers. Maybe try to detect this at startup or one every day?

[gizmocuz]

Sorry I jumped to fast to the conclusion it was fixed.
Unfortunately, After a day, when I want to enter my Dockge interface to enable a docker contrainer, it displays no containers and the below error is back:

dockge  | Trace: TypeError: composeStatus is not iterable
dockge  |     at Function.isComposeExitClean (/app/backend/stack.ts:459:43)
dockge  |     at process.processTicksAndRejections (node:internal/process/task_q                                                                                                                             ueues:105:5)
dockge  |     at async Function.statusConvert (/app/backend/stack.ts:487:20)
dockge  |     at async Function.getStackList (/app/backend/stack.ts:389:29)
dockge  |     at async DockgeServer.sendStackList (/app/backend/dockge-server.ts                                                                                                                             :601:33)
dockge  |     at process.unexpectedErrorHandler (/app/backend/dockge-server.ts:8                                                                                                                             9:21)
dockge  |     at process.emit (node:events:519:28)
dockge  |     at process.emit (/usr/local/lib/node_modules/tsx/dist/suppress-war                                                                                                                             nings.cjs:1:472)
dockge  |     at emitUnhandledRejection (node:internal/process/promises:252:13)
dockge  |     at throwUnhandledRejectionsMode (node:internal/process/promises:38                                                                                                                             8:19)
dockge  |     at processPromiseRejections (node:internal/process/promises:475:17                                                                                                                             )
dockge  |     at process.processTicksAndRejections (node:internal/process/task_q                                                                                                                             ueues:106:32)
dockge  | If you keep encountering errors, please report to https://github.com/c                                                                                                                             mcooper1980/dockge

I stoped Dockge, deleted the data folder, started it again, and needed to enter a username/password, at the moment I pressed OK, the same error shows up.

Stopped the container again, deleted the data folder and executed the below command

docker system prune -f -a --volumes && docker compose pull && docker compose up -d --force-recreate

and we are back in business.

[cmcooper1980]

Unfortunately, I can't seem to duplicate the issue...I have two Dockge instances (3 at the time I tried to duplicate your issue with your compose) running for a few days now since the last update and the stacks remain populated. From your compose, I see you should be on the latest. Maybe see if you can duplicate the issue by spinning up a 2nd instance, give it a different port, different container name, and give it a data-test folder...maybe even try the cmcooper1980/dockge:image-management tag and see if it is the same outcome.

Differences in my environment vs your compose are that Dockge is in its own directory while all my stacks are in another (only kept this way due to starting docker way back with DockSTARTer). I just mapped them accordingly in my compose.

so in my home directory
|-dockge
|-.docker (stacks directory)
____|-nginx
____|-gotify
____|-seaxng
|-.config (stacks app data)
____|-nginx
____|-gotify
____|-searxng

[gizmocuz]

Thank you for your response, I tried spinning up a new instance with the image you mentioned.
Everything the same as above, new folder of course, new contrainer name, new port
I browse to the port, and the setup page is displaying. I enter a username (admin) and a password ($3*SAvE^aLoTwaNQMea98w4JXl$MmQi7)
Nothing happens when pressing the create button....
I look at the browsers developers console and see:

Failed to fetch Turnstile site key from socket: Turnstile site key is not configured.
Uncaught (in promise) TypeError: r is not a function
at Dz. (index-D06mIgcU.js:1036:47931)
at Dz.onack (index-D06mIgcU.js:1036:35170)
at Dz.onpacket (index-D06mIgcU.js:1036:34381)
at di.emit (index-D06mIgcU.js:1036:5538)
at index-D06mIgcU.js:1036:40393

Not giving up (coz I noticed this before), I go again to the root page (removed the /setup)

I can see the containers now... I will monitor this for a few days

But, since I am not the only one with this issue, would it be OK for you to make sure that this error would not happen again?
(By checking the composeStatus in function isComposeExitClean (/app/backend/stack.ts:459:43))
(Maybe give a warning if something is wrong with it, or log to the console)
I don't think it is null, it is something, but not what is expected

(I use the Edge browser, but that should not be the issue)

[gizmocuz]

Ps. is the new image obfuscated? Because that would not be good for troubleshooting ;)

[gizmocuz]

What I also noticed is that my dockgetest container is showing up active, but at the very bottom of the list and is grayed out somewhat

[gizmocuz]

And... I see a dockGETest inactive... which is my test...

If I click on the inactive one, I see my compose file

services:
  dockge:
    image: cmcooper1980/dockge:image-management
    container_name: dockge_test
    restart: unless-stopped
    ports:
      - 5002:5001
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./data:/app/data
      - /opt:/opt
    environment:
      # Tell Dockge where to find the stacks
      - DOCKGE_STACKS_DIR=/opt
    networks:
      - backend
networks:
  backend:
    external: true

If I click on the active (but grayed one) I get the message

This stack is not managed by Dockge.

Question: Who thinks of the name? The name of the container is not taken from the container_name of the compose file.
I noticed this before. But how can we change this name?
(I guess it is the name of the folder... not sure if that is a desired situation when someone is using container_name in the compose file)

[gizmocuz]

Still working perfect!

[cmcooper1980]

that's great

[Kitof]

Same issue here with fresh install.