-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VNC server is off for 2.53.1 (latest) docker images #291
Comments
hi @MegaUkrainian thanks for reporting this.. this change actually directly goes against @gurukiran007 's change in #256 , so i'd like to make sure that he has some input on this. |
As an alternative to b3c9fa5 it might be possible to start x11vnc in the entry script as seluser as well? |
it does work as root, and i'm going to leave it that way, really doesn't matter who is running the vnc server. i've pushed up a new version of the 2.53.1, 3.0.0-beta3 and 3.0.0-beta4 versions, and they are currently building. they will push when done (and of course, if tests pass.) will close this issue when they are released |
Your fix was my first local quick fix as well. Just tried running x11vnc as seluser now, because I don't know why it does matter where the secret is stored. |
well it matters since whoever runs i will say, that running the |
pushed all versions |
👍 |
Hello,
I faced with an issue of connecting to firefox/chrome-node-debug for 2.53.1 (latest) images. According to the logs, starting of the vncserver was failed:
I think the following statement was failed while image was creating:
Please check. Thank you in advance.
The text was updated successfully, but these errors were encountered: