linuxserver / docker-webtop

Ubuntu, Alpine, Arch, and Fedora based Webtop images, Linux in a web browser supporting popular desktop environments.
GNU General Public License v3.0
1.97k stars 205 forks source link

container does not start any more #255

Closed leonardpitzu closed 3 months ago

leonardpitzu commented 3 months ago

Is there an existing issue for this?

Current Behavior

container does not finish starting

Expected Behavior

starting...

Steps To Reproduce

create a new container from ubuntu-xfce start the container

Environment

- OS: Linux
- distro package manager

CPU architecture

x86-64

Docker creation

linux:
    container_name: "linux"
    image: linuxserver/webtop:ubuntu-xfce
    mem_limit: 4096m
    network_mode: bridge
#    security_opt:
#      - seccomp:unconfined
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Bucharest
      - SUBFOLDER=/linux/
      - TITLE=Linux
      - LC_ALL=en_US.UTF-8
      - DISABLE_IPV6=true
    volumes:
      - "/volume1/docker/linux:/config:rw"
      - "/volume1/development:/development:rw"
      - "/volume1/web:/web:rw"
      - /var/run/docker.sock:/var/run/docker.sock
    ports:
      - 3000:3000
      - 3001:3001
    devices:
      - /dev/dri:/dev/dri
    shm_size: "1gb"
#    privileged: true
    restart: unless-stopped

Container logs

Xvnc KasmVNC 1.2.0 - built Jul 27 2024 19:05:59
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
19
github-actions[bot] commented 3 months ago

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

thelamer commented 3 months ago

That is the normal output, I cannot replicate this:

working

To test try pulling your volumes out to run it ephemerally just to see if it boots on your machine. Also set seccomp unconfined if running on an older base system. Also drop the /dev/dri mount as well just to test.

leonardpitzu commented 3 months ago

/dev/dri had a problem and upon rebooting the machine everything is good. have no idea what was wrong but the issue can be closed. thanks for your support.