You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 30, 2021. It is now read-only.
Please make sure that the boxes below are checked before you submit your issue. Thank you!
Operating System
Within EKS Cluster using Amazon Linux 2 for woker nodes
Image version
I have latest version of this image. Upgrade with docker pull elgalu/selenium
If I don't have latest version of this image and can't upgrade, I will specify which one I'm using.
Docker version
I have latest version of docker and I will specify here the output of docker --version
18.09.9ce-2.amzn2
If I don't have latest version of docker I will specify which version with docker --version output
Docker-Compose
(if using docker-compose)
I have latest version of docker-compose and I will specify here the output of docker-compose --version
If I don't have latest version of docker-compose I will specify which version with docker-compose --version output
I'm using this image with zalenium on an AWS EKS cluster. I'm getting the following error for some sessions:
(The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '3.141.59', revision: '82b03c358b', time: '2019-04-30T22:04:50'
System info: host: 'zalenium-40000-zqdfl', ip: 'x.x.x.x', os.name: 'Linux', os.arch: 'amd64', os.version: '4.14.177-139.254.amzn2.x86_64', java.version: '1.8.0_252'
Driver info: driver.version: unknown
remote stacktrace: #0 0x557da7916579 <unknown>
I see the following error in 'Browser Driver Log' from zalenium dashboard:
[1592305744.882][INFO]: Launching chrome: /usr/bin/google-chrome --disable-background-networking --disable-client-side-phishing-detection --disable-default-apps --disable-hang-monitor --disable-popup-blocking --disable-prompt-on-repost --disable-sync --enable-automation --enable-blink-features=ShadowDOMV0 --enable-logging --ignore-certificate-errors --load-extension=/tmp/.com.google.Chrome.8fJz8G/internal --log-level=0 --no-first-run --password-store=basic --remote-debugging-port=0 --test-type=webdriver --use-mock-keychain --user-data-dir=/tmp/.com.google.Chrome.feemyV data:,
[464:464:0616/210910.397741:ERROR:browser_main_loop.cc(1473)] Unable to open X display.
[0616/110910.424436:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly
[0616/110910.425151:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly
[1592305750.461][INFO]: [d9b2d26873a265e34602a4b842264daa] RESPONSE InitSession ERROR unknown error: Chrome failed to start: crashed.
(unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)[1592305750.461][DEBUG]: Log type 'driver' lost 0 entries on destruction[1592305750.461][DEBUG]: Log type 'browser' lost 0 entries on destruction
The text was updated successfully, but these errors were encountered:
Please make sure that the boxes below are checked before you submit your issue. Thank you!
Operating System
Image version
I have latest version of this image. Upgrade with
docker pull elgalu/selenium
If I don't have latest version of this image and can't upgrade, I will specify which one I'm using.
Docker version
docker --version
18.09.9ce-2.amzn2
docker --version
outputDocker-Compose
(if using docker-compose)
I have latest version of docker-compose and I will specify here the output of
docker-compose --version
If I don't have latest version of docker-compose I will specify which version with
docker-compose --version
outputI'm using this image with zalenium on an AWS EKS cluster. I'm getting the following error for some sessions:
I see the following error in 'Browser Driver Log' from zalenium dashboard:
The text was updated successfully, but these errors were encountered: