Hi all together,
currently i try to install two additional docker container which a working fine on my Proxmox system (i want to move them now to OMV which hosts several other container):
- JDownloader (jlesage/jdownloader-2:latest)
- TinyMediaManager (romancin/tinymediamanager:latest-v4)
Both provide a GUI powered by VNC, accessable via Browser.
I use a docker compose file for that. Example for JDownloader:
version: '3'
services:
jdownloader:
image: jlesage/jdownloader-2
container_name: jdownloader
restart: always
ports:
- "32793:5800"
environment:
- DISPLAY_WIDTH=1280
- DISPLAY_HEIGHT=720
- TZ=Europe/Berlin
volumes:
- "./volumes/config:/config"
- /mnt/Download:/output
Display More
This File is working perfect on my Proxmox inside a LXC.
Unfortunately under OMV6 the container is created, i access the webpage 192.168.x.x:32793 in my browser and i can see the 1280x720 VNC-Window in the TAB.
Usualy the JDownloader-GUI is now getting displayed inside the Window. The Window stays black and nothing happens ...
The provided LOG from Portainer shows this and i have no clue whats wrong here:
> Warning: Could not resolve keysym XF86Macro28
> Warning: Could not resolve keysym XF86Macro29
> Warning: Could not resolve keysym XF86Macro30
> Warning: Could not resolve keysym XF86MacroRecordStart
> Warning: Could not resolve keysym XF86MacroRecordStop
> Warning: Could not resolve keysym XF86MacroPresetCycle
> Warning: Could not resolve keysym XF86MacroPreset1
> Warning: Could not resolve keysym XF86MacroPreset2
> Warning: Could not resolve keysym XF86MacroPreset3
> Warning: Could not resolve keysym XF86KbdLcdMenu1
> Warning: Could not resolve keysym XF86KbdLcdMenu2
> Warning: Could not resolve keysym XF86KbdLcdMenu3
> Warning: Could not resolve keysym XF86KbdLcdMenu4
> Warning: Could not resolve keysym XF86KbdLcdMenu5
Errors from xkbcomp are not fatal to the X server
19/10/2022 10:20:02 Using X display :0
19/10/2022 10:20:02 rootwin: 0x42 reswin: 0x200001 dpy: 0x18dc9040
19/10/2022 10:20:02
19/10/2022 10:20:02 ------------------ USEFUL INFORMATION ------------------
19/10/2022 10:20:02 X DAMAGE available on display, using it for polling hints.
19/10/2022 10:20:02 To disable this behavior use: '-noxdamage'
19/10/2022 10:20:02
19/10/2022 10:20:02 Most compositing window managers like 'compiz' or 'beryl'
19/10/2022 10:20:02 cause X DAMAGE to fail, and so you may not see any screen
19/10/2022 10:20:02 updates via VNC. Either disable 'compiz' (recommended) or
19/10/2022 10:20:02 supply the x11vnc '-noxdamage' command line option.
19/10/2022 10:20:02 X COMPOSITE available on display, using it for window polling.
19/10/2022 10:20:02 To disable this behavior use: '-noxcomposite'
19/10/2022 10:20:02
19/10/2022 10:20:02 Wireframing: -wireframe mode is in effect for window moves.
19/10/2022 10:20:02 If this yields undesired behavior (poor response, painting
19/10/2022 10:20:02 errors, etc) it may be disabled:
19/10/2022 10:20:02 - use '-nowf' to disable wireframing completely.
19/10/2022 10:20:02 - use '-nowcr' to disable the Copy Rectangle after the
19/10/2022 10:20:02 moved window is released in the new position.
19/10/2022 10:20:02 Also see the -help entry for tuning parameters.
19/10/2022 10:20:02 You can press 3 Alt_L's (Left "Alt" key) in a row to
19/10/2022 10:20:02 repaint the screen, also see the -fixscreen option for
19/10/2022 10:20:02 periodic repaints.
19/10/2022 10:20:02 GrabServer control via XTEST.
19/10/2022 10:20:02
19/10/2022 10:20:02 Scroll Detection: -scrollcopyrect mode is in effect to
19/10/2022 10:20:02 use RECORD extension to try to detect scrolling windows
19/10/2022 10:20:02 (induced by either user keystroke or mouse input).
19/10/2022 10:20:02 If this yields undesired behavior (poor response, painting
19/10/2022 10:20:02 errors, etc) it may be disabled via: '-noscr'
19/10/2022 10:20:02 Also see the -help entry for tuning parameters.
19/10/2022 10:20:02 You can press 3 Alt_L's (Left "Alt" key) in a row to
19/10/2022 10:20:02 repaint the screen, also see the -fixscreen option for
19/10/2022 10:20:02 periodic repaints.
19/10/2022 10:20:02
19/10/2022 10:20:02 XKEYBOARD: number of keysyms per keycode 7 is greater
19/10/2022 10:20:02 than 4 and 51 keysyms are mapped above 4.
19/10/2022 10:20:02 Automatically switching to -xkb mode.
19/10/2022 10:20:02 If this makes the key mapping worse you can
19/10/2022 10:20:02 disable it with the "-noxkb" option.
19/10/2022 10:20:02 Also, remember "-remap DEAD" for accenting characters.
19/10/2022 10:20:02
19/10/2022 10:20:02 X FBPM extension not supported.
Xlib: extension "DPMS" missing on display ":0".
19/10/2022 10:20:02 X display is not capable of DPMS.
19/10/2022 10:20:02 --------------------------------------------------------
19/10/2022 10:20:02
19/10/2022 10:20:02 Default visual ID: 0x21
19/10/2022 10:20:02 Read initial data from X display into framebuffer.
19/10/2022 10:20:02 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120
19/10/2022 10:20:02
19/10/2022 10:20:02 X display :0 is 32bpp depth=24 true color
19/10/2022 10:20:02
19/10/2022 10:20:02 Listening for VNC connections on TCP port 5900
19/10/2022 10:20:02
19/10/2022 10:20:02 Xinerama is present and active (e.g. multi-head).
19/10/2022 10:20:02 Xinerama: number of sub-screens: 1
19/10/2022 10:20:02 Xinerama: no blackouts needed (only one sub-screen)
19/10/2022 10:20:02
19/10/2022 10:20:02 fb read rate: 1202 MB/sec
19/10/2022 10:20:02 fast read: reset -wait ms to: 10
19/10/2022 10:20:02 fast read: reset -defer ms to: 10
19/10/2022 10:20:02 The X server says there are 10 mouse buttons.
19/10/2022 10:20:02 screen setup finished.
19/10/2022 10:20:02
The VNC desktop is: 03977d58abf7:0
0
******************************************************************************
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?
The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval. It should work with any VNC viewer. Try it by running:
x11vnc -ncache 10 ...
One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching
[services.d] starting app...
[app] starting JDownloader 2...
[services.d] done.
[jdsupervisor] JDownloader2 not started yet. Proceeding...
Display More
The same exact same happens with the TinyMediaManager image.
Is it possible that i have to change something, since both are related to a VNC-powered docker image ?
Many thanks in advance
EDIT: I tried the shown "-ncache" option from the end of the LOG. But no success