I have a nested container running in debian lxc which I am trying to mount /var/run/docker.sock but the container cannot access it. Is this not possible in incus? I did verify my docker-default app armor profile mentions incus.
ERR Cannot create Docker client error=“permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.47/version": dial unix /var/run/docker.sock: socket: permission denied” provider=docker
I saw other folks are using docker.io instead of docker-ce, does docker-ce have issues with apparmor that docker.io doesn’t when using incus? Should I be using docker.io?
So it looks like its not just /var/run/docker.sock but even just trying to run some containers (such as Uptime Kuma) doesn’t work unless I set privileged: true on the container itself because it can’t listen on a socket. So to work around I’m having to make most of my containers privileged. I don’t want to disable apparmor completely and I tried a workaround to only ignore the incus namespace but that did not work.
2025-93-27T10:33:48-07:00 [SERVICES] INFO: Starting nscd
Trace: Error: read ENOTCONN
at tryReadStart (node:net:710:20)
at Socket._read (node:net:725:5)
at Readable.read (node:internal/streams/readable:539:12)
at Socket.read (node:net:781:39)
at new Socket (node:net:498:12)
at Object.Socket (node:net:367:41)
at createSocket (node:internalschild_process:329:14)
at ChildProcess.spawn (node:internalschild_process:444:23)
at spawn (node:child_process:761:9)
at Object.execFile (node:child_process:351:17) §
| errno: -167,
] code: ‘ENOTCONN’,
}| syscall: 'read’
] at process.unexpectedErrorHandler (/app/server/server.js:19605:13)
] at process.emit (node:events:517:28)