'Error: spawn docker ENOENT' on v1.3.4

[sasagar]

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

The error below appears every 6 secondes.

2023-12-20T01:53:21Z [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) {
   errno: -2,
   code: 'ENOENT',
   syscall: 'spawn docker',
   path: 'docker',
   spawnargs: [ 'compose', 'ps', '--format', 'json' ]
 }

👟 Reproduction steps

1. pull latest docker image
2. run docker compose up -d && docker compose logs -f
3. the logs appears.

👀 Expected behavior

No error appears.

😓 Actual Behavior

The error appears every 6 sec.

Dockge Version

1.3.4

💻 Operating System and Arch

CentOS Stream 9 / Docker

🌐 Browser

Chrome 120.0.6099.110

🐋 Docker Version

Docker version 24.0.7, build afdd53b

🟩 NodeJS Version

No response

📝 Relevant log output

2023-12-20T01:52:40Z [SERVER] INFO: Welcome to dockge!
2023-12-20T01:52:40Z [SERVER] INFO: NODE_ENV: production
2023-12-20T01:52:40Z [SERVER] INFO: Server Type: HTTP
2023-12-20T01:52:40Z [SERVER] INFO: Data Dir: ./data/
2023-12-20T01:52:40Z [DB] INFO: Database Type: sqlite
2023-12-20T01:52:40Z [SERVER] INFO: Connected to the database
2023-12-20T01:52:40Z [SERVER] INFO: Listening on 5001
2023-12-20T01:52:45Z [SERVER] INFO: Socket connected!
2023-12-20T01:52:45Z [AUTH] INFO: Login by token. IP=192.168.224.1
2023-12-20T01:52:45Z [AUTH] INFO: Username from JWT: <userid>
2023-12-20T01:52:45Z [AUTH] INFO: Successfully logged in user <userid>. IP=192.168.224.1
2023-12-20T01:52:46Z [SERVER] INFO: Socket connected!
2023-12-20T01:52:46Z [AUTH] INFO: Login by token. IP=192.168.224.1
2023-12-20T01:52:46Z [AUTH] INFO: Username from JWT: <userid>
2023-12-20T01:52:46Z [AUTH] INFO: Successfully logged in user <userid>. IP=192.168.224.1
2023-12-20T01:52:46Z [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) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn docker',
  path: 'docker',
  spawnargs: [ 'compose', 'ps', '--format', 'json' ]
}

[louislam]

Cannot reproduce, but the latest version is 1.3.5.

[sasagar]

is it?
I could not find the version of 1.3.5 on Release page.

anyway, I got the image as latest from docker hub.

[sasagar]

and now, I restart with running command sepaerately, it disappers.

I'm not sure, but maybe there is something to be said for not running commands in succession when restarting Docker.

[mountaindude]

Update 2:
Scratch that. Error still happens. There were no error messages for a while, so I assumed the problem was sorted.
Error message remains.

---

Update 1:
It was indeed a permissions issue.
I had done some of the prep wok as root, no good.
Deleted everything, then started from scratch using my personal user (which has permissions to Docker).

All good then.

---

I am seeing the same thing on today's latest (=1.4.1).

Running from another directory compared to the getting-started instructions, but I did use the compose.yaml online generator.

Could be a permissions issue?
What user should be used to start Dockge (using docker compose up)?
root or regular user (that's part of the Docker group)?

compose.yaml:

version: "3.8"
services:
  dockge:
    image: louislam/dockge:1
    restart: unless-stopped
    ports:
      - 5001:5001
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./data:/app/data
      # Stacks Directory
      # ⚠️ READ IT CAREFULLY. If you did it wrong, your data could end up writing into a WRONG PATH.
      # ⚠️ 1. FULL path only. No relative path (MUST)
      # ⚠️ 2. Left Stacks Path === Right Stacks Path (MUST)
      - /data/apps/dockge/stacks:/data/apps/dockge/stacks
    environment:
      # Tell Dockge where to find the stacks
      - DOCKGE_STACKS_DIR=/data/apps/dockge/stacks

[vladaurosh]

Getting the same error with 1.4.1 docker image.

[markusglaetzner]

Getting the same error with 1.4.1. All my stacks are not usable in dockge - I get "This stack is not managed by Dockge.". See my opened issue #359

[beaumsc]

I was getting this error because I was not using docker compose V2 plugin. With docker compose v1, the command is docker-compose (with hyphen). The command without the hyphen docker compose (as was used according to the error log) requires docker compose version 2.