You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason I'm running the xinit command is because vncsession can't be run as root (I'm working on a non-root solution). With the above script running once I docker run my image, I am able to visit http://localhost:6080/vnc.html whereby I am first prompted to click on "Connect" and then enter a password - the password in this context would be VNC password (which in my example is just 'password').
I have been looking through the following novnc/noVNC#522 and I am wondering if anyone could provide an example of how I could use --auth-pligin' or --token-plugin` to authenticate the user's session instead of prompting the user for the VNC password, as in the end product, the user wouldn't know of the VNC password/shouldn't have to enter a VNC password.
If this is not possible, can the VNC password be propagated to this form instead?
UPDATE: For reference, these are the packages I am installing:
# RUN zypper install --no-recommends -y vncserver
RUN zypper install --no-recommends -y xorg-x11-server
RUN zypper install --no-recommends -y xorg* xterm xauth xorg-x11-fonts xorg-x11-fonts-core xorg-x11-Xvnc tigervnc
# python3-numpy to accelerate processing in python websockify
RUN zypper install -y xorg-x11-Xvnc-novnc python3-numpy python3-websockify python3-PyJWT python-websockify-common
RUN zypper install -y nginx
The text was updated successfully, but these errors were encountered:
I have a Docker image that when I run it, runs a bash script that has the following content:
The reason I'm running the xinit command is because
vncsession
can't be run as root (I'm working on a non-root solution). With the above script running once Idocker run
my image, I am able to visit http://localhost:6080/vnc.html whereby I am first prompted to click on "Connect" and then enter a password - the password in this context would be VNC password (which in my example is just 'password').I have been looking through the following novnc/noVNC#522 and I am wondering if anyone could provide an example of how I could use
--auth-pligin' or
--token-plugin` to authenticate the user's session instead of prompting the user for the VNC password, as in the end product, the user wouldn't know of the VNC password/shouldn't have to enter a VNC password.If this is not possible, can the VNC password be propagated to this form instead?
UPDATE: For reference, these are the packages I am installing:
The text was updated successfully, but these errors were encountered: