[FEAT] Native VNC port exposing

[DenisBalan]

Is this a new feature request?

• I have searched the existing issues

Wanted change

currently 3000 (http is exposed, serves GUI for firefox) which is great
requesting also ability, in addition to port 3000 to have native vnc port exposed, if there is such a posibility?

based on the doc, seems to be possible https://kasmweb.com/kasmvnc/docs/1.0.0/configuration.html#network

similar issue which doesnt provide any work-able solution #8

in jlesage/firefox this is working, but i'll like to stick to linuxserver suite.

Reason for change

better interoperability and monitoring with native vnc protocol

Proposed code change

n/a

[github-actions]

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

[Roxedus]

Not possible, the protocol is not pure VNC afaik. linuxserver/docker-chromium#25 (comment)

[DenisBalan]

@Roxedus but is there any way of exposing an internal vnc server?
perhaps with other toolings from inside of the container?

tried tightvncserver but it struggles to connect to proper display, which is being used by kasmvnc internally..

[aptalca]

For what benefit? Kasmvnc's web interface is miles better than any vnc client I've seen.

[DenisBalan]

for ex i want to run every N minutes some screenshot tools, or even stream output via ffmpeg and store it for auditing purposes, etc.

also connecting to vnc, seems to be more "native" rather simply web
not mean to replace accessing via web, its in addition

[aptalca]

I'm afraid those aren't primary use cases of this image and would be considered edge cases.

If you want something native (for whatever reason), we have rdesktop images that you can access via rdp.

For vnc, we no longer offer client access as kasmvnc is way superior and even does lossless.