starred/dockge-louislam
1
0
Fork 0
mirror of https://github.com/louislam/dockge.git synced 2026-03-03 02:06:55 -05:00
Code Issues 99 Projects Packages Wiki Activity

Compose files not seen #58

New issue
Closed
opened 2026-02-20 13:10:07 -05:00 by deekerman · 6 comments
deekerman commented 2026-02-20 13:10:07 -05:00
Owner
Copy link

Originally created by @Aviortheking on GitHub (Dec 6, 2023).

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

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

I have no compose files seen + it seems that it stop detecting state of compose
image
the token shown in my compose is out of date

👟 Reproduction steps

  • create a docker-compose.yml out of the /opt/stacks folder file with
version: "3.3"
services:
  uptime-kuma:
    restart: unless-stopped
    volumes:
      - ./data:/app/data
      - /var/run/docker.sock:/var/run/docker.sock:ro
    image: louislam/uptime-kuma:1
    networks:
      - coolify-infra
    labels:
      - traefik.enable=true
      - traefik.http.routers.uptime-kuma.rule=Host(`uptime.dzeio.com`)
      - traefik.http.services.uptime-kuma.loadbalancer.server.port=3001
      - traefik.http.routers.uptime-kuma.tls.certresolver=letsencrypt
  • run docker-compose up -d
  • run docker-compose stop
  • delete the docker-compose.yml file

I think you have to create a compose file an up it once, stop it and delete the compose file
(out of dockge stacks folder)

as the container 491e4c1cac31a1be74020030eb10e5d259a2a820a501ab10e1b8223b36e642f7 was made in another folder but the compose file is not present anymore (also the container is down)

👀 Expected behavior

we should be able to see the list of stacks and manipulate active containers

😓 Actual Behavior

we don't see the list of stacks and can't manipulate active composes

Dockge Version

1.3.2

💻 Operating System and Arch

Linux SRV1 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) x86_64 GNU/Linux

🌐 Browser

Firefox 119.0.1

🐋 Docker Version

Docker version 20.10.24+dfsg1, build 297e128

🟩 NodeJS Version

No response

📝 Relevant log output

dockge_1  |     at process.unexpectedErrorHandler (/app/backend/dockge-server.ts:76:21)
dockge_1  |     at process.emit (node:events:514:28)
dockge_1  |     at process.emit (/pnpm/global/5/.pnpm/tsx@4.5.0/node_modules/tsx/dist/suppress-warnings.cjs:1:472)
dockge_1  |     at emit (node:internal/process/promises:149:20)
dockge_1  |     at processPromiseRejections (node:internal/process/promises:283:27)
dockge_1  |     at process.processTicksAndRejections (node:internal/process/task_queues:96:32)
dockge_1  | If you keep encountering errors, please report to https://github.com/louislam/dockge
dockge_1  | Trace: Error: Process exited with code 1
dockge_1  |     at ChildProcess.done (/app/node_modules/.pnpm/promisify-child-process@4.1.2/node_modules/promisify-child-process/index.cjs:70:19)
dockge_1  |     at ChildProcess.emit (node:events:514:28)
dockge_1  |     at ChildProcess.emit (node:domain:489:12)
dockge_1  |     at maybeClose (node:internal/child_process:1091:16)
dockge_1  |     at ChildProcess._handle.onexit (node:internal/child_process:302:5) {
dockge_1  |   code: 1,
dockge_1  |   signal: null,
dockge_1  |   stdout: '',
dockge_1  |   stderr: 'No label "com.docker.compose.project.config_files" set on container "491e4c1cac31a1be74020030eb10e5d259a2a820a501ab10e1b8223b36e642f7" of compose project\n'
dockge_1  | }
Originally created by @Aviortheking on GitHub (Dec 6, 2023). ### ⚠️ 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 I have no compose files seen + it seems that it stop detecting state of compose ![image](https://github.com/louislam/dockge/assets/15822031/2619b726-9a02-4b54-925f-5221d8d22d31) *the token shown in my compose is out of date* ### 👟 Reproduction steps - create a `docker-compose.yml` out of the `/opt/stacks` folder file with ``` version: "3.3" services: uptime-kuma: restart: unless-stopped volumes: - ./data:/app/data - /var/run/docker.sock:/var/run/docker.sock:ro image: louislam/uptime-kuma:1 networks: - coolify-infra labels: - traefik.enable=true - traefik.http.routers.uptime-kuma.rule=Host(`uptime.dzeio.com`) - traefik.http.services.uptime-kuma.loadbalancer.server.port=3001 - traefik.http.routers.uptime-kuma.tls.certresolver=letsencrypt ``` - run `docker-compose up -d` - run `docker-compose stop` - delete the `docker-compose.yml` file I think you have to create a compose file an up it once, stop it and delete the compose file (out of dockge stacks folder) as the container `491e4c1cac31a1be74020030eb10e5d259a2a820a501ab10e1b8223b36e642f7` was made in another folder but the compose file is not present anymore (also the container is down) ### 👀 Expected behavior we should be able to see the list of stacks and manipulate active containers ### 😓 Actual Behavior we don't see the list of stacks and can't manipulate active composes ### Dockge Version 1.3.2 ### 💻 Operating System and Arch Linux SRV1 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21) x86_64 GNU/Linux ### 🌐 Browser Firefox 119.0.1 ### 🐋 Docker Version Docker version 20.10.24+dfsg1, build 297e128 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output ```shell dockge_1 | at process.unexpectedErrorHandler (/app/backend/dockge-server.ts:76:21) dockge_1 | at process.emit (node:events:514:28) dockge_1 | at process.emit (/pnpm/global/5/.pnpm/tsx@4.5.0/node_modules/tsx/dist/suppress-warnings.cjs:1:472) dockge_1 | at emit (node:internal/process/promises:149:20) dockge_1 | at processPromiseRejections (node:internal/process/promises:283:27) dockge_1 | at process.processTicksAndRejections (node:internal/process/task_queues:96:32) dockge_1 | If you keep encountering errors, please report to https://github.com/louislam/dockge dockge_1 | Trace: Error: Process exited with code 1 dockge_1 | at ChildProcess.done (/app/node_modules/.pnpm/promisify-child-process@4.1.2/node_modules/promisify-child-process/index.cjs:70:19) dockge_1 | at ChildProcess.emit (node:events:514:28) dockge_1 | at ChildProcess.emit (node:domain:489:12) dockge_1 | at maybeClose (node:internal/child_process:1091:16) dockge_1 | at ChildProcess._handle.onexit (node:internal/child_process:302:5) { dockge_1 | code: 1, dockge_1 | signal: null, dockge_1 | stdout: '', dockge_1 | stderr: 'No label "com.docker.compose.project.config_files" set on container "491e4c1cac31a1be74020030eb10e5d259a2a820a501ab10e1b8223b36e642f7" of compose project\n' dockge_1 | } ```
deekerman 2026-02-20 13:10:07 -05:00
deekerman commented 2026-02-20 13:10:10 -05:00
Author
Owner
Copy link

@louislam commented on GitHub (Dec 6, 2023):

The reproduce steps is not clear and don't quite understand, because you said you deleted the compose file.

Isn't expected? because you deleted the compose file and won't able to show in the list.

@louislam commented on GitHub (Dec 6, 2023): The reproduce steps is not clear and don't quite understand, because you said you deleted the compose file. Isn't expected? because you deleted the compose file and won't able to show in the list.
deekerman commented 2026-02-20 13:10:10 -05:00
Author
Owner
Copy link

@Aviortheking commented on GitHub (Dec 6, 2023):

another explanation :

  • create a docker-compose.yml out of the /opt/stacks folder file with
version: "3.3"
services:
  uptime-kuma:
    restart: unless-stopped
    volumes:
      - ./data:/app/data
      - /var/run/docker.sock:/var/run/docker.sock:ro
    image: louislam/uptime-kuma:1
    networks:
      - coolify-infra
    labels:
      - traefik.enable=true
      - traefik.http.routers.uptime-kuma.rule=Host(`uptime.dzeio.com`)
      - traefik.http.services.uptime-kuma.loadbalancer.server.port=3001
      - traefik.http.routers.uptime-kuma.tls.certresolver=letsencrypt
  • run docker-compose up -d
  • run docker-compose stop
  • delete the docker-compose.yml file

You will have a stopped container with a non existing compose file

@Aviortheking commented on GitHub (Dec 6, 2023): another explanation : - create a `docker-compose.yml` out of the `/opt/stacks` folder file with ``` version: "3.3" services: uptime-kuma: restart: unless-stopped volumes: - ./data:/app/data - /var/run/docker.sock:/var/run/docker.sock:ro image: louislam/uptime-kuma:1 networks: - coolify-infra labels: - traefik.enable=true - traefik.http.routers.uptime-kuma.rule=Host(`uptime.dzeio.com`) - traefik.http.services.uptime-kuma.loadbalancer.server.port=3001 - traefik.http.routers.uptime-kuma.tls.certresolver=letsencrypt ``` - run `docker-compose up -d` - run `docker-compose stop` - delete the `docker-compose.yml` file You will have a stopped container with a non existing compose file
deekerman commented 2026-02-20 13:10:10 -05:00
Author
Owner
Copy link

@Aviortheking commented on GitHub (Dec 6, 2023):

I'm not quite sure why it happens, but the containers linked to the errors are containers that had their lifecycle like above

@Aviortheking commented on GitHub (Dec 6, 2023): I'm not quite sure why it happens, but the containers linked to the errors are containers that had their lifecycle like above
deekerman commented 2026-02-20 13:10:10 -05:00
Author
Owner
Copy link

@louislam commented on GitHub (Dec 6, 2023):

If you want to delete a stack, you must use docker compose down, stop is not OK. You should check docker compose docs if you have any questions.

It is a docker question, not a bug.

@louislam commented on GitHub (Dec 6, 2023): If you want to delete a stack, you must use `docker compose down`, `stop` is not OK. You should check docker compose docs if you have any questions. It is a docker question, not a bug.
deekerman commented 2026-02-20 13:10:10 -05:00
Author
Owner
Copy link

@Aviortheking commented on GitHub (Dec 9, 2023):

welp the containers were bassically stopped because they were meant to be restarted so we didn't want to have networks and all removed

@Aviortheking commented on GitHub (Dec 9, 2023): welp the containers were bassically stopped because they were meant to be restarted so we didn't want to have networks and all removed
deekerman commented 2026-02-20 13:10:10 -05:00
Author
Owner
Copy link

@Aviortheking commented on GitHub (Dec 9, 2023):

but even so, stopped containers should not crash Dockge compose recognition, it should skip them at least I think

@Aviortheking commented on GitHub (Dec 9, 2023): but even so, stopped containers should not crash Dockge compose recognition, it should skip them at least I think
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
pr-merges
fix-console
switch-back-to-npm
1.5.X
fix-353
fix-337
multiple
revert-303-compose
compose
fix-env3
s
build-windows
update-deploy
fix-check-update
env2
fix-234
env-follow-up
child-process-async
sort
reset-password
healthcheck
arm-runner
fix-cpu
urls
websocket
rollout
remove-version
close-terminal
fix-inactive
rebase-discussion-form
docs
improvements
down
check-ts
eslint
release-process
feat-use-monospace-fonts
wip
1.5.0
1.4.2
1.4.1
1.4.0
1.4.0-beta.0
1.3.5
1.3.4
1.3.3
1.3.2
1.3.1
1.3.0
1.2.0
1.1.1
1.1.0
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0
Labels
Clear labels   
bug

   
feature-request

   
help

   
help wanted

   
invalid-format

   
need-reproduce-steps

   
question

   
security

   
upstream

   
wontfix
No labels
bug
feature-request
help
help wanted
invalid-format
need-reproduce-steps
question
security
upstream
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dockge-louislam#58
No description provided.