docker-kodi icon indicating copy to clipboard operation
docker-kodi copied to clipboard

Possible x11docker X server options

Open mviereck opened this issue 6 years ago • 5 comments

I tried some different possible X server setups for kodi.

  • Within already running X:
    • quite well:
      • --hostdisplay --gpu
      • --hostdisplay --trusted --hostipc
      • --weston-xwayland with and without --gpu
    • less of interest:
      • --xephyr (stable but slow because it does not support --gpu)
      • --xpra (terribly slow without --gpu; with --gpu it would use --weston-xwayland in background).
    • crashes:
      • --nxagent
  • From console:
    • quite well with and without --gpu:
      • --xorg
      • --weston-xwayland
  • Within pure Wayland without X/Xwayland:
    • quite well:
      • --weston-xwayland
    • issues with non-covered panels of Wayland compositor:
      • --xwayland

Dependencies to check: --weston-xwayland: weston and Xwayland --xorg: xorg (console or, within X, setup of /etc/X11/Xwrapper.config --hostdisplay: already running X server (environment DISPLAY) --xephyr: Xephyr and already running X server --xwayland: Xwayland and already running Wayland (environment WAYLAND_DISPLAY)

--gpu: works well with open source drivers on host. Pitfall: NVIDIA cards run quite well with nouveau driver on host. But with non-free-nvidia driver the very same nvidia driver version must be installed in image. (At this point I always think of Linus Thorvalds and his gesture towards NVIDIA ...).

--fullscreen enables fullscreen mode of --xephyr and --weston-xwayland. Without that it is also nice to see kodi catched in a window. :-p Though, if this window is closed, kodi crashes screechy.

The most reliable option for all possible setups and situations is --weston-xwayland and it provides the best isolation from host while still being performant. Drawback: weston and Xwayland are rarely installed already.

mviereck avatar Apr 12 '18 21:04 mviereck

Just a note: The automated X server choice of x11docker should fit well for erichough/kodi. Your current command example is

$ x11docker --xorg                                 \
            --vt 7                                 \
            --pulseaudio                           \
            --wm none                              \                
            --gpu                                  \
            --homedir /host/path/to/kodi/home      \
            -- -v /host/path/to/media:/media:ro -- \
            erichough/kodi

You can reduce it to:

$ x11docker --pulseaudio                           \
            --gpu                                  \
            --homedir /host/path/to/kodi/home      \
            -- -v /host/path/to/media:/media:ro -- \
            erichough/kodi

You can still set --vt 7, it does not hurt other X server options. --wm=none avoids to load a needless window manager with --xorg, but can be disturbing if it is started on a desktop. x11docker would try to run in a nested X server that might not be available.

mviereck avatar Feb 17 '19 22:02 mviereck

using the latest x11docker 6.1.1 (debian 9) "-- -v /host/path/to/media:/media:ro" does not work. I was only able to workaround with --share /path/to/destination/ ...of course then it is not bound as /media...but at least I could gain access to my media.

SicLuceatLux avatar Aug 12 '19 10:08 SicLuceatLux

using the latest x11docker 6.1.1 (debian 9) "-- -v /host/path/to/media:/media:ro" does not work. I

It works here. Maybe you have missed the second -- in that line?

mviereck avatar Aug 14 '19 08:08 mviereck

using the latest x11docker 6.1.1 (debian 9) "-- -v /host/path/to/media:/media:ro" does not work.

Also works normally for me. @SicLuceatLux if you're still having trouble please post your full x11docker run command so we can take a look.

ehough avatar Aug 14 '19 16:08 ehough

thx for your answers ! have to recheck it

SicLuceatLux avatar Aug 15 '19 20:08 SicLuceatLux