Open kullervo16 opened 7 years ago
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:
FROM selenium/node-chrome:3.0.1
USER root
RUN chmod -R 777 /opt/selenium
RUN echo "2a54b938e3f511e6bf01fe55135034f3" > /etc/machine-id
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 :-)