Skip to content
This repository has been archived by the owner on Jun 30, 2021. It is now read-only.

crash on docker run #391

Open
3 tasks done
v0idp opened this issue Jul 29, 2020 · 2 comments
Open
3 tasks done

crash on docker run #391

v0idp opened this issue Jul 29, 2020 · 2 comments

Comments

@v0idp
Copy link

v0idp commented Jul 29, 2020

Please make sure that the boxes below are checked before you submit your issue. Thank you!

Operating System

  • I provided my operating system name and version, e.g. output of uname -a Ubuntu 20.04 LTS

Image version

  • I have latest version of this image. Upgrade with docker pull elgalu/selenium

Docker version

  • I have latest version of docker and I will specify here the output of docker --version 3.141.59-334

Getting this error when starting the image. any idea why this could happen ?

-- INFO: Docker Img. Version: 3.141.59-334
-- INFO: Chrome..... Version: 84.0.4147.105
-- INFO: Firefox.... Version: 75.0
-- INFO: Using Selenium.....: 3.141.59
supervisord --version=4.0.0.dev0
tail: cannot open '' for reading: No such file or directory
==> /var/log/cont/wait-xvfb.1.log <==
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x296
    class:    TrueColor
    depth:    32 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
Done wait-xvfb.sh

==> /var/log/cont/fluxbox-tryouts-stderr.log <==

==> /var/log/cont/selenium-node-chrome-stdout.log <==

==> /var/log/cont/firefox_browser.log <==
webdriver.log.file has been discontinued.
Please send us a PR if you know how to set the path for the Firefox browser logs.

==> /var/log/cont/vnc-tryouts-stderr.40675.log <==

==> /var/log/cont/vnc-stdout.log <==

==> /var/log/cont/selenium-node-chrome-stderr.log <==

==> /var/log/cont/selenium-node-firefox-stderr.log <==

==> /var/log/cont/xmanager-stderr.log <==

==> /var/log/cont/xterm-stdout.log <==

==> /var/log/cont/vnc-stderr.log <==

==> /var/log/cont/vnc-tryouts-stdout.40675.log <==

==> /var/log/cont/xmanager-stdout.log <==

==> /var/log/cont/docker-selenium-status.log <==

==> /var/log/cont/xvfb-tryouts-stderr.log <==
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

==> /var/log/cont/fluxbox-tryouts-stdout.log <==

==> /var/log/cont/selenium-node-firefox-stdout.log <==

==> /var/log/cont/supervisord.log <==

==> /var/log/cont/xterm-stderr.log <==

==> /var/log/cont/chrome_browser.log <==
Setting --user-data-dir=/home/seluser/chrome-user-data-dir
breaks the ability of clients to set Chrome options via the capabilities.
Please send us a PR if you know how to set the path for the Firefox browser logs.

==> /var/log/cont/wait-xmanager-stdout.log <==

==> /var/log/cont/xvfb-tryouts-stdout.log <==

==> /var/log/cont/wait-xvfb-stdout.log <==
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x296
    class:    TrueColor
    depth:    32 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
Done wait-xvfb.sh

==> /var/log/cont/wait-xvfb.2.log <==
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x296
    class:    TrueColor
    depth:    32 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
Done wait-xvfb.sh
Error: The directory named as part of the path /var/run/sele/supervisord.pid does not exist
For help, use /usr/local/bin/supervisord -h```
@mohammadsaleh
Copy link

I have this problem too.

@v0idp
Copy link
Author

v0idp commented Oct 17, 2020

I have this problem too.

hey there. Little info on my end here. I was using a worker on gitlab to compile this image and the issue was that the worker for some reason wasn't able to get the supervisord dependencies properly I assume. No error in the pipeline tho.

So the error still persists for me.

EDIT: for the time being I'm compiling it locally and pushing it to my gitlab registry.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants