User permissions error inside container while starting hub docker image

[gael-wogenstahl]

Meta -

Image(s): hub
Docker-Selenium Image Version(s): 3.4.0-einsteinium
OS: Ubuntu Desktop 14.04

Expected Behavior -

Running the hub docker image as explained in the documentation should result in a container running.

Actual Behavior -

Trying to run the hub docker image results in container exiting right away with the following error :

/opt/bin/entry_point.sh: line 6: /opt/selenium/config.json: Permission denied

This issue looks a lot like #405

[luispabon]

Same here:

selenium                 | /opt/bin/entry_point.sh: line 6: /opt/selenium/config.json: Permission denied
selenium                 | starting selenium hub with configuration:
selenium                 | {
selenium                 |   "host": null,
selenium                 |   "port": 4444,
selenium                 |   "role": "hub",
selenium                 |   "maxSession": ,
selenium                 |   "newSessionWaitTimeout": ,
selenium                 |   "capabilityMatcher": "org.openqa.grid.internal.utils.DefaultCapabilityMatcher",
selenium                 |   "throwOnCapabilityNotPresent": ,
selenium                 |   "jettyMaxThreads": ,
selenium                 |   "cleanUpCycle": ,
selenium                 |   "browserTimeout": ,
selenium                 |   "timeout": ,
selenium                 |   "debug": 
selenium                 | }

The weird thing is that it starts fine on my desktop running Ubuntu 17.04 but not on a centos machine.

Obviously that json is invalid.

[luispabon]

See this gist https://gist.github.com/luispabon/89aeed53deb87a96c22becf6997188c0

[gael-wogenstahl]

I managed to fix the problem by deactivating user namespace in Docker ("userns-remap" in /etc/docker/daemon.json).
I don't need that functionality on my desktop computer right now but I might need it on the server.
All in all this points to a user permission problem on files located in /opt/selenium directory as stated in #405 .

[diemol]

Hi @gael-wogenstahl, @luispabon,

I just tried with the most recent release, and here is the output:

docker run -it selenium/hub:3.6.0-americium /opt/bin/entry_point.sh

Unable to find image 'selenium/hub:3.6.0-americium' locally
3.6.0-americium: Pulling from selenium/hub
Digest: sha256:838358c2e069a76aaee2e50961c42218c4d98abb77ec27c05022b89b350529c1
Status: Downloaded newer image for selenium/hub:3.6.0-americium
starting selenium hub with configuration:
{
  "host": null,
  "port": 4444,
  "role": "hub",
  "maxSession": 5,
  "newSessionWaitTimeout": -1,
  "capabilityMatcher": "org.openqa.grid.internal.utils.DefaultCapabilityMatcher",
  "throwOnCapabilityNotPresent": true,
  "jettyMaxThreads": -1,
  "cleanUpCycle": 5000,
  "browserTimeout": 0,
  "timeout": 30,
  "debug": false
}
19:44:28.163 INFO - Selenium build info: version: '3.6.0', revision: '6fbf3ec767'
19:44:28.164 INFO - Launching Selenium Grid hub
2017-10-03 19:44:28.911:INFO::main: Logging initialized @1264ms to org.seleniumhq.jetty9.util.log.StdErrLog
19:44:28.957 INFO - Will listen on 4444
2017-10-03 19:44:29.089:INFO:osjs.Server:main: jetty-9.4.5.v20170502
2017-10-03 19:44:29.165:INFO:osjs.session:main: DefaultSessionIdManager workerName=node0
2017-10-03 19:44:29.165:INFO:osjs.session:main: No SessionScavenger set, using defaults
2017-10-03 19:44:29.172:INFO:osjs.session:main: Scavenging every 600000ms
2017-10-03 19:44:29.198:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler@525f1e4e{/,null,AVAILABLE}
2017-10-03 19:44:29.241:INFO:osjs.AbstractConnector:main: Started ServerConnector@12d3a4e9{HTTP/1.1,[http/1.1]}{0.0.0.0:4444}
2017-10-03 19:44:29.246:INFO:osjs.Server:main: Started @1597ms
19:44:29.260 INFO - Nodes should register to http://172.17.0.2:4444/grid/register/
19:44:29.260 INFO - Selenium Grid hub is up and running

Maybe something got fixed in the meantime? Could you please try again?

[diemol]

Closing this issue due to inactivity, please reopen if the issue still exists.