Closed masterkain closed 5 years ago
@masterkain Does it work if you don't set WD_INSTALL_DIR
to the mounted volume and use the default ~/.webdrivers
instead?
I get the "Deleting .../chroemdriver" message in the log file even it's working. I am suspecting maybe it's a permission issue. Can you try setting WD_INSTALL_DIR to somewhere where you should have write permission such as /tmp/ or ~/ ? Are you able to run it on your own laptop?
I also think it is a permissions issue based on this:
2019-07-27 21:49:54 DEBUG Webdrivers /usr/src/app/webdrivers/chromedriver is already downloaded
2019-07-27 21:49:54 DEBUG Webdrivers making System call: ["/usr/src/app/webdrivers/chromedriver", "--version"]
2019-07-27 21:49:54 DEBUG Webdrivers No Such File or Directory: /usr/src/app/webdrivers/chromedriver
The file is found, but webdrivers
isn't able to extract the version. Also, the file is not being deleted at the end as shown in the log (2019-07-27 21:50:01 DEBUG Webdrivers Deleting /usr/src/app/webdrivers/chromedriver
). That line is being logged incorrectly and has been fixed under 1af4557db4a86d17e5a47ae0c774c99a14ddb812.
I recommend trying a different location where you have proper permissions (maybe your project root?) and see if you get the same error. I am closing this Issue for now, but I'd happy to debug this further when you respond.
hello, sorry I had to move on quick and had not time to get back to this issue, I thank everyone for their continued support; I plan to test again soon, will report back any finding, your work is always appreciated. 🥇
seeing a similar issue with a similar env : Alpine Linux container, any call to update or run the Webdrivers endup with a file in the expected path but not ability to use it as calls to it will always endup with "No such file or directory". User is root so I don't know how permissions would matter here.
Hello, I get a similar problem and I found the reason for me in the logic, I set to use chrome as the browser but I only install chromium on OS then, I install chrome and everything works well sorry for my panic English, hope this helps you.
Summary
Library downloads and instantly removes the binaries.
Debug Info
Expected Behavior
Binaries to persist for the CI to run.
Actual Behavior
I tried almost anything to get a Rails 5.2 app working with a chrome/chromium headless instance on docker. this is what happens, even if I run the update webdrivers task
bin/rails webdrivers:chromedriver:update
before the spec run:I have no parallel spec, disabled bootsnap, disabled spring, tested with a single spec, no guard etc.
the volume is mounted in docker as local named volume but behavior doesn't change with other volumes types or none at all.
ENV WD_INSTALL_DIR=/usr/src/app/webdrivers