hosting with containerd.sock #220

New issue

Open

opened 2026-02-20 13:12:19 -05:00 by deekerman · 0 comments

deekerman commented

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

Owner

Originally created by @xyphanajay on GitHub (Aug 10, 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

I'm running it in a ubuntu server via docker compose but I have containerd.sock in place of usual docker.sock. App is breaking with the following logs.

👟 Reproduction steps

Docker compose config

services:
  dockge:
    image: louislam/dockge:1
    restart: always
    ports:
      - 5001:5001
    volumes:
      - /run/containerd/containerd.sock:/var/run/docker.sock
      - ./data:/app/data

👀 Expected behavior

Docker socket connectivity in dockge web UI.

😓 Actual Behavior

2025-08-10T17:12:34Z [SERVER] INFO: Welcome to dockge!
2025-08-10T17:12:34Z [SERVER] INFO: NODE_ENV: production
2025-08-10T17:12:34Z [SERVER] INFO: Server Type: HTTP
2025-08-10T17:12:34Z [SERVER] INFO: Data Dir: ./data/
2025-08-10T17:12:34Z [DB] INFO: Database Type: sqlite
2025-08-10T17:12:34Z [SERVER] INFO: Connected to the database
2025-08-10T17:12:34Z [SERVER] INFO: Listening on 5001
2025-08-10T17:12:54Z [AUTH] INFO: Origin is not set, IP: ::ffff:172.28.0.1
2025-08-10T17:12:54Z [SERVER] INFO: Socket connected (direct)
2025-08-10T17:12:55Z [AUTH] INFO: Login by token. IP=172.28.0.1
2025-08-10T17:12:55Z [AUTH] INFO: Username from JWT: admin
2025-08-10T17:12:55Z [AUTH] INFO: Successfully logged in user admin. IP=172.28.0.1
Trace: Error: Process exited with code 1
    at ChildProcess.done (/app/node_modules/promisify-child-process/index.cjs:70:19)
    at ChildProcess.emit (node:events:518:28)
    at maybeClose (node:internal/child_process:1101:16)
    at ChildProcess._handle.onexit (node:internal/child_process:304:5) {
  code: 1,
  signal: null,
  stdout: '',
  stderr: 'Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.48/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.config-hash%22%3Atrue%2C%22com.docker.compose.project%22%3Atrue%7D%7D": net/http: HTTP/1.x transport connection broken: malformed HTTP response "\\x00\\x00\\x06\\x04\\x00\\x00\\x00\\x00\\x00\\x00\\x05\\x00\\x00@\\x00".\n' +
    '* Are you trying to connect to a TLS-enabled daemon without TLS?\n'
}
    at process.unexpectedErrorHandler (/app/backend/dockge-server.ts:89:21)
    at process.emit (node:events:518:28)
    at process.emit (/usr/local/lib/node_modules/tsx/dist/suppress-warnings.cjs:1:472)
    at emitUnhandledRejection (node:internal/process/promises:252:13)
    at throwUnhandledRejectionsMode (node:internal/process/promises:388:19)
    at processPromiseRejections (node:internal/process/promises:475:17)
    at process.processTicksAndRejections (node:internal/process/task_queues:106:32)
If you keep encountering errors, please report to https://github.com/louislam/dockge

Dockge Version

dockge:1

💻 Operating System and Arch

Ubuntu x86_64

🌐 Browser

Zen

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

Originally created by @xyphanajay on GitHub (Aug 10, 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 I'm running it in a ubuntu server via docker compose but I have `containerd.sock` in place of usual `docker.sock`. App is breaking with the following logs. ### 👟 Reproduction steps Docker compose config ``` services: dockge: image: louislam/dockge:1 restart: always ports: - 5001:5001 volumes: - /run/containerd/containerd.sock:/var/run/docker.sock - ./data:/app/data ``` ### 👀 Expected behavior Docker socket connectivity in dockge web UI. ### 😓 Actual Behavior ``` 2025-08-10T17:12:34Z [SERVER] INFO: Welcome to dockge! 2025-08-10T17:12:34Z [SERVER] INFO: NODE_ENV: production 2025-08-10T17:12:34Z [SERVER] INFO: Server Type: HTTP 2025-08-10T17:12:34Z [SERVER] INFO: Data Dir: ./data/ 2025-08-10T17:12:34Z [DB] INFO: Database Type: sqlite 2025-08-10T17:12:34Z [SERVER] INFO: Connected to the database 2025-08-10T17:12:34Z [SERVER] INFO: Listening on 5001 2025-08-10T17:12:54Z [AUTH] INFO: Origin is not set, IP: ::ffff:172.28.0.1 2025-08-10T17:12:54Z [SERVER] INFO: Socket connected (direct) 2025-08-10T17:12:55Z [AUTH] INFO: Login by token. IP=172.28.0.1 2025-08-10T17:12:55Z [AUTH] INFO: Username from JWT: admin 2025-08-10T17:12:55Z [AUTH] INFO: Successfully logged in user admin. IP=172.28.0.1 Trace: Error: Process exited with code 1 at ChildProcess.done (/app/node_modules/promisify-child-process/index.cjs:70:19) at ChildProcess.emit (node:events:518:28) at maybeClose (node:internal/child_process:1101:16) at ChildProcess._handle.onexit (node:internal/child_process:304:5) { code: 1, signal: null, stdout: '', stderr: 'Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.48/containers/json?all=1&filters=%7B%22label%22%3A%7B%22com.docker.compose.config-hash%22%3Atrue%2C%22com.docker.compose.project%22%3Atrue%7D%7D": net/http: HTTP/1.x transport connection broken: malformed HTTP response "\\x00\\x00\\x06\\x04\\x00\\x00\\x00\\x00\\x00\\x00\\x05\\x00\\x00@\\x00".\n' + '* Are you trying to connect to a TLS-enabled daemon without TLS?\n' } at process.unexpectedErrorHandler (/app/backend/dockge-server.ts:89:21) at process.emit (node:events:518:28) at process.emit (/usr/local/lib/node_modules/tsx/dist/suppress-warnings.cjs:1:472) at emitUnhandledRejection (node:internal/process/promises:252:13) at throwUnhandledRejectionsMode (node:internal/process/promises:388:19) at processPromiseRejections (node:internal/process/promises:475:17) at process.processTicksAndRejections (node:internal/process/task_queues:106:32) If you keep encountering errors, please report to https://github.com/louislam/dockge ``` ### Dockge Version dockge:1 ### 💻 Operating System and Arch Ubuntu x86_64 ### 🌐 Browser Zen ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output ```shell ```