Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VNC Issues - Container has become very unstable after recent updates #164

Closed
1 task done
Altycoder opened this issue Oct 23, 2024 · 3 comments
Closed
1 task done

Comments

@Altycoder
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Been using this image/container for a while, but after the last 2-3 updates has suddenly become very unstable and unusable.

Getting lots of VNC errors like in the image attached:
Screenshot 2024-10-23 155752

Expected Behavior

Should not freeze and crash

Steps To Reproduce

Open calibre via port 8080 (mapped to 8082 in my case) and calibre is very sluggish (far more sluggish than usual) then within 10-15 seconds get a blue screen with VNC error

Environment

- OS: Arch LTS Kernel
- How docker service was installed: from Arch repo

CPU architecture

x86-64

Docker creation

calibre:
    image: ghcr.io/linuxserver/calibre
    container_name: calibre
    networks:
      - media    
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
      - UMASK=002
      - DRINODE=/dev/dri/renderD128
      - CLI_ARGS="–auth-mode=basic"
    volumes:
      - ${DOCKER_DIR}/calibre/config:/config:rw
      - ${DOCKER_DIR}/calibre/upload:/uploads:rw
      - ${DOCKER_DIR}/calibre/plugins:/plugins:rw
      - ${DOCKER_DIR}/calibre/CalibreLibrary:/Calibre_Library:rw
    ports:
      - 8082:8080
      - 8083:8081
    devices:
      - /dev/dri:/dev/dri
    restart: unless-stopped

Container 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:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: v7.20.0-ls308
Build-date: 2024-10-23T06:42:34+00:00
───────────────────────────────────────
    
**** creating video group videopjlb with id 985 ****
**** adding /dev/dri/card1 to video group videopjlb with id 985 ****
**** creating video group video5uuk with id 989 ****
**** adding /dev/dri/renderD128 to video group video5uuk with id 989 ****
[custom-init] No custom files found, skipping...
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
Xvnc KasmVNC 1.3.2 - built Oct 19 2024 19:06:02
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
[ls.io-init] done.
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
19
Obt-Message: Xinerama extension is not present on the server
xvnc_get_formats
WARNING: Kernel has no file descriptor comparison support: Operation not permitted
 2024-10-23 16:00:52,457 [INFO] websocket 0: got client connection from 127.0.0.1
 2024-10-23 16:00:52,469 [PRIO] Connections: accepted: @192.168.1.107_1729695652.458301::websocket
@thelamer
Copy link
Member

Try with seccomp unconfined
WARNING: Kernel has no file descriptor comparison support: Operation not permitted this makes me think it is a kernel syscall.

@Altycoder
Copy link
Author

OK will give that a try. It just seems way more sluggish than usual as well, and as Calibre is very slow anyway....

@Altycoder
Copy link
Author

Looks like this has fixed it, thanks. After a server restart this morning things also feel a bit snappier as well which is good.

@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants