[BUG] Issue Running Docker Inside Sealskin Webtop Container

[tangentmove]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hello Team,

I am starting the Sealskin server using the following command:

docker run -d --name=sealskin --privileged \
  -e START_DOCKER=true \
  -e TZ=Etc/UTC \
  -e HOST_URL="192.168.1.191" \
  -p 8443:8443 \
  -p 8000:8000 \
  -v ./config:/config \
  -v ./storage:/storage \
  -v /var/run/docker.sock:/var/run/docker.sock \
  --restart unless-stopped \
  lscr.io/linuxserver/sealskin:latest

I have also enabled the “Start Docker-in-Docker” option in the Sealskin server application template.

From the Sealskin server, I installed the MATE Debian app (lscr.io/linuxserver/webtop:debian-mate). However, I am unable to run Docker commands inside this container.

I can see that the Docker client is available inside the MATE container, but Docker itself does not appear to be functional. Am I missing any additional configuration or setup steps?

Thank you for your assistance.

Best regards,
Tangent

Expected Behavior

.

Steps To Reproduce

mentioned above

Environment

- OS:
- How docker service was installed:

CPU architecture

x86-64

Docker creation

docker ps -a

Container logs

none

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[gitranch]

Enabling following docker options is causing webscoket disconnect

thread '<unnamed>' panicked at src/lib.rs:341:14: Failed to allocate GBM buffer: Os { code: 13, kind: PermissionDenied, message: "Permission denied" } note: run with RUST_BACKTRACE=1` environment variable to display a backtrace
INFO:selkies.main:Starting mode 'websockets'...
INFO:selkies.main:Starting Selkies in 'websockets' mode.
INFO:data_websocket:pcmflux library found. Audio capture is available.
[Wayland] Initializing GL Renderer using device: /dev/dri/renderD128
INFO:data_websocket:pixelflux library found. Striped encoding modes available.
VMware: No 3D enabled (0, Success).
VMware: No 3D enabled (0, Success).
VMware: No 3D enabled (0, Success).
VMware: No 3D enabled (0, Success).
INFO:root:Expected C js_config_t size (from ctypes): 1354 bytes
[Wayland] Warning: Failed to bind EGL to Wayland Display (Optional): EglExtensionNotSupported(["EGL_WL_bind_wayland_display"])
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied

thread '' panicked at src/lib.rs:341:14:
Failed to allocate GBM buffer: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
INFO:selkies.main:Starting mode 'websockets'...
INFO:selkies.main:Starting Selkies in 'websockets' mode.
INFO:data_websocket:pcmflux library found. Audio capture is available.
[Wayland] Initializing GL Renderer using device: /dev/dri/renderD128
INFO:data_websocket:pixelflux library found. Striped encoding modes available.
VMware: No 3D enabled (0, Success).
VMware: No 3D enabled (0, Success).
VMware: No 3D enabled (0, Success).
VMware: No 3D enabled (0, Success).
INFO:root:Expected C js_config_t size (from ctypes): 1354 bytes
[Wayland] Warning: Failed to bind EGL to Wayland Display (Optional): EglExtensionNotSupported(["EGL_WL_bind_wayland_display"])
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied

thread '' panicked at src/lib.rs:341:14:
Failed to allocate GBM buffer: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
INFO:selkies.main:Starting mode 'websockets'...
INFO:selkies.main:Starting Selkies in 'websockets' mode.
INFO:data_websocket:pcmflux library found. Audio capture is available.
[Wayland] Initializing GL Renderer using device: /dev/dri/renderD128
INFO:data_websocket:pixelflux library found. Striped encoding modes available.
VMware: No 3D enabled (0, Success).
VMware: No 3D enabled (0, Success).
VMware: No 3D enabled (0, Success).
VMware: No 3D enabled (0, Success).
INFO:root:Expected C js_config_t size (from ctypes): 1354 bytes
[Wayland] Warning: Failed to bind EGL to Wayland Display (Optional): EglExtensionNotSupported(["EGL_WL_bind_wayland_display"])
KMS: DRM_IOCTL_MODE_CREATE_DUMB failed: Permission denied

thread '' panicked at src/lib.rs:341:14:
Failed to allocate GBM buffer: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace`

[gitranch]

this happening after upgrading sealskin to 0.1.35

[thelamer]

Yeah you are running a VM with a vmware video adapter. I did not write "This will break things" for fun I wrote that because this is precisely what can happen.

Priv mode mounts in the entire device tree, in our container we assume a mounted in video device wants to be used but a vmware video devices is about as useful as a wet blanket.

You will notice that none of these containers ever recommend priv mode, just that technically with it flagged we will try to run DinD inside the container.

This is the auto section that binds up a video card if there is only one in the container.

https://github.com/linuxserver/docker-baseimage-selkies/blob/master/root/etc/s6-overlay/s6-rc.d/init-selkies-config/run#L264-L273