-
Notifications
You must be signed in to change notification settings - Fork 64
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
firefox cannot connect #2
Comments
hey @kullervo16 ! actually, i'm the maintainer of the selenium docker images and i can tell you, that we are way past 2.53.1. maybe give Selenium 3 a shot, and use the image version: 3 for node-firefox, and hub? |
thanks for the quick reply. Got it working, however some observations that might be useful for other people:
does the trick. The /etc/machine-id fixes a dbus warning
Conclusion : moved to chrome iso firefox, and our tests are running again :-) |
@ddavison ... Is there any option to run the selenium docker containers without root access? In my organization, the open-shift admin is not interested to give the root access to everyone. Pls advise. |
When I use your templates in OSE 3.1 and selenium 2.53.1 encounter some problems with the node-firefox image. It needs to have access to /opt/selenium, if I relax that condition it starts up fine, registers itself in the grid but I get this error:
I have the same error when I use a standalone image from either selenium, some other people or when I package my working VM config... Is there anything special on openshift? Does this container need to be priviledged?
Any suggestions are more than welcome... been fighting this thing for a week now, starts working on my system :-)
The text was updated successfully, but these errors were encountered: