RobCherry / docker-chromedriver

Docker container for creating ChromeDriver servers
99 stars 74 forks source link

chrome start failing #14

Open spatchava opened 6 years ago

spatchava commented 6 years ago

unable to start the chrome:

Logs are as follows: M-C02W329QHV2R:dashfrontendtest spatchava$ docker run --name chromedriver -p 127.0.0.1::4444 -e CHROMEDRIVER_WHITELISTED_IPS='' robcherry/docker-chromedriver:latest 2018-06-18 22:26:32,512 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. 2018-06-18 22:26:32,512 INFO Included extra file "/etc/supervisor/conf.d/chromedriver.conf" during parsing 2018-06-18 22:26:32,512 INFO Included extra file "/etc/supervisor/conf.d/tinywm.conf" during parsing 2018-06-18 22:26:32,512 INFO Included extra file "/etc/supervisor/conf.d/xvfb.conf" during parsing 2018-06-18 22:26:32,522 INFO RPC interface 'supervisor' initialized 2018-06-18 22:26:32,523 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2018-06-18 22:26:32,523 INFO supervisord started with pid 1 2018-06-18 22:26:33,531 INFO spawned: 'xvfb' with pid 8 2018-06-18 22:26:33,536 INFO spawned: 'tinywm' with pid 9 2018-06-18 22:26:33,539 INFO spawned: 'chromedriver' with pid 10 2018-06-18 22:26:33,553 INFO exited: tinywm (exit status 1; not expected) 2018-06-18 22:26:33,560 INFO exited: chromedriver (exit status 1; not expected) 2018-06-18 22:26:34,563 INFO success: xvfb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-06-18 22:26:34,567 INFO spawned: 'tinywm' with pid 19 2018-06-18 22:26:34,570 INFO spawned: 'chromedriver' with pid 20 2018-06-18 22:26:34,578 INFO exited: chromedriver (exit status 1; not expected) 2018-06-18 22:26:35,583 INFO success: tinywm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-06-18 22:26:36,590 INFO spawned: 'chromedriver' with pid 25 2018-06-18 22:26:36,600 INFO exited: chromedriver (exit status 1; not expected) 2018-06-18 22:26:39,610 INFO spawned: 'chromedriver' with pid 30 2018-06-18 22:26:39,620 INFO exited: chromedriver (exit status 1; not expected) 2018-06-18 22:26:40,623 INFO gave up: chromedriver entered FATAL state, too many start retries too quickly

RobCherry commented 6 years ago

Try running with the --privileged option in the docker command. For some light reading, check out https://github.com/RobCherry/docker-chromedriver/issues/7.