Skip to content
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

Closed
MikeShysh opened this issue Oct 3, 2016 · 7 comments
Closed

VNC server is off for 2.53.1 (latest) docker images #291

MikeShysh opened this issue Oct 3, 2016 · 7 comments

Comments

@MikeShysh
Copy link

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:

Waiting xvfb...
05:55:43.976 INFO - Launching a Selenium Grid node
03/10/2016 05:55:44 passing arg to libvncserver: -rfbport
03/10/2016 05:55:44 passing arg to libvncserver: 5900
Enter VNC password: stty: 'standard input': Inappropriate ioctl for device
fgets: No such file or directory
stty: 'standard input': Inappropriate ioctl for device
x11vnc -usepw: could not find a password to use.

I think the following statement was failed while image was creating:

RUN mkdir -p ~/.vnc \
 && x11vnc -storepasswd secret ~/.vnc/passwd

Please check. Thank you in advance.

ddavison added a commit that referenced this issue Oct 3, 2016
@ddavison
Copy link
Member

ddavison commented Oct 3, 2016

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.

@TheBay0r
Copy link

TheBay0r commented Oct 3, 2016

As an alternative to b3c9fa5 it might be possible to start x11vnc in the entry script as seluser as well?

@ddavison
Copy link
Member

ddavison commented Oct 3, 2016

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

@TheBay0r
Copy link

TheBay0r commented Oct 3, 2016

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.
Thanks for taking care!

@ddavison
Copy link
Member

ddavison commented Oct 3, 2016

well it matters since whoever runs x11vnc -usepw..., the -usepw param will look for ~/.vnc. if root is running the command, then it will look at ~root/.vnc. if seluser runs that command, it will look for ~seluser/.vnc.

i will say, that running the x11vnc command from seluser with the ~seluser/.vnc command would probably work, but since the entry_point.sh is already running as root, might as well keep it that way, and put the passwd file in ~root/.vnc 👍

@ddavison
Copy link
Member

ddavison commented Oct 3, 2016

pushed all versions

@ddavison ddavison closed this as completed Oct 3, 2016
@gurukiran007
Copy link

👍

@lock lock bot locked and limited conversation to collaborators Aug 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants