[BUG] ubuntu-kde docker integration is broken since noble upgrade?
hgw77 opened this issue · comments
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
It seems since ubuntu-kde-b5810752-ls31 docker is no longer working. This is also the update from jammy to noble. I run my webtop with privileged rights and docker was working without issues until ubuntu-kde-7d928019-ls30
Expected Behavior
ps aux | grep docker
root 49 0.0 0.0 216 72 ? S 16:32 0:00 s6-supervise svc-docker
root 604 0.2 0.1 2209148 86596 ? Ssl 16:32 0:00 dockerd --host=unix:///var/run/docker.sock -l error
root 1015 0.2 0.0 2168124 48000 ? Ssl 16:32 0:00 containerd --config /var/run/docker/containerd/containerd.toml --log-level error
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
Steps To Reproduce
ps aux | grep docker
root 50 0.0 0.0 216 72 ? S 16:35 0:00 s6-supervise svc-docker
root 1065 0.0 0.0 181356 3784 ? Ss 16:36 0:00 bash ./run svc-docker
docker ps
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Environment
- OS:
- How docker service was installed:CPU architecture
x86-64
Docker creation
docker run -d \
--name=workspace-desktop \
--hostname="$(hostname)" \
--env PUID=0 \
--env PGID=0 \
--env CUSTOM_USER="$USER" \
--env PASSWORD="$DESKTOP_PASSWORD" \
--env TZ="Europe/Berlin" \
--env TITLE=Workspace-KDE \
--env WS_USER="$WS_USER" \
--publish 3010:3010 \
--privileged \
--security-opt seccomp=unconfined \
--restart unless-stopped \
--shm-size="1gb" \
lscr.io/linuxserver/webtop:ubuntu-kde-version-b5810752Container logs
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 0
User GID: 0
───────────────────────────────────────
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Xvnc KasmVNC 1.2.0 - built Apr 22 2024 16:20:29
Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
See http://kasmweb.com for information on KasmVNC.
Underlying X server release 12014000, The X.Org Foundation
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Could not resolve keysym XF86CameraAccessEnable
> Warning: Could not resolve keysym XF86CameraAccessDisable
> Warning: Could not resolve keysym XF86CameraAccessToggle
> Warning: Could not resolve keysym XF86NextElement
> Warning: Could not resolve keysym XF86PreviousElement
> Warning: Could not resolve keysym XF86AutopilotEngageToggle
> Warning: Could not resolve keysym XF86MarkWaypoint
> Warning: Could not resolve keysym XF86Sos
> Warning: Could not resolve keysym XF86NavChart
> Warning: Could not resolve keysym XF86FishingChart
> Warning: Could not resolve keysym XF86SingleRangeRadar
> Warning: Could not resolve keysym XF86DualRangeRadar
> Warning: Could not resolve keysym XF86RadarOverlay
> Warning: Could not resolve keysym XF86TraditionalSonar
> Warning: Could not resolve keysym XF86ClearvuSonar
> Warning: Could not resolve keysym XF86SidevuSonar
> Warning: Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Could not resolve keysym XF86CameraAccessEnable
> Warning: Could not resolve keysym XF86CameraAccessDisable
> Warning: Could not resolve keysym XF86CameraAccessToggle
> Warning: Could not resolve keysym XF86NextElement
> Warning: Could not resolve keysym XF86PreviousElement
> Warning: Could not resolve keysym XF86AutopilotEngageToggle
> Warning: Could not resolve keysym XF86MarkWaypoint
> Warning: Could not resolve keysym XF86Sos
> Warning: Could not resolve keysym XF86NavChart
> Warning: Could not resolve keysym XF86FishingChart
> Warning: Could not resolve keysym XF86SingleRangeRadar
> Warning: Could not resolve keysym XF86DualRangeRadar
> Warning: Could not resolve keysym XF86RadarOverlay
> Warning: Could not resolve keysym XF86TraditionalSonar
> Warning: Could not resolve keysym XF86ClearvuSonar
> Warning: Could not resolve keysym XF86SidevuSonar
> Warning: Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
sed: couldn't flush stdout: Invalid argument
sed: couldn't flush stdout: Invalid argument
sed: couldn't flush stdout: Invalid argument
sed: couldn't flush stdout: Invalid argument
sed: couldn't flush stdout: Invalid argument
sed: couldn't flush stdout: Invalid argument
2024-06-04 16:24:53,946 [INFO] websocket 0: got client connection from 127.0.0.1
2024-06-04 16:24:53,959 [PRIO] Connections: accepted: @10.180.3.127_1717511093.946850::websocket
sed: couldn't flush stdout: Invalid argument
sed: couldn't flush stdout: Invalid argument
sed: couldn't flush stdout: Invalid argument
sed: couldn't flush stdout: Invalid argument
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Looks like an issue with the DIND script that we grab from here https://github.com/moby/moby/blob/master/hack/dind
Can you try deleting /usr/local/bin/dind and restarting the container?
I cannot replicate this:
docker run --rm -it --privileged -p 3000:3000 linuxserver/webtop:ubuntu-kde bash
Two things never do this:
--env PUID=0 \
--env PGID=0 \
And you do not need seccomp unconfined mixed with privileged, use my minimal run command check it works and pile stuff on from there see what is breaking it.
Internally we have determined it revolves around the kernel version on the host, 6.6, 6.7 and 6.8 seem to work fine, but 6.1.0 and 5.15 which we tested do not.
If you cannot upgrade the kernel on your host I would highly recommend using debian-kde, (bookworm is nearly identical to Noble outside of some semi-ver bumps).
Thank you for looking into this :-) I have Kernel Version 6.1 👍 that explains why it is not working
can be closed, problem was the kernel of the host