selenium-ide: Something is wrong with the selenium-side-runner when running dockerfile

Meta -

OS: Windows 10 (ubuntu in dockerfile) Selenium IDE Version: v3.2.0-beta.1 Selenium SIDE Runner Version: 3.2.0-beta.1 Node version: npm: 5.6.0, node: v8.11.3 Browser: Chrome

Browser Version:

Expected Behavior -

The selenium-side-runner workes fine in Windows 10 with the command:

selenium-side-runner -c chromeOptions.args=[headless] project.side

CMD in dockerfile:

CMD [“selenium-side-runner”, “-c”, “chromeOptions.args=[headless]”, “/tmp/project.side”]

But when I run the dockerfile I get this error:

`fs.js:675 return binding.read(fd, buffer, offset, length, position); ^

Error: EISDIR: illegal operation on a directory, read at Object.fs.readSync (fs.js:675:18) at tryReadSync (fs.js:540:20) at Object.fs.readFileSync (fs.js:583:19) at _commander2.default.args.map.p (/usr/local/lib/node_modules/selenium-side-runner/dist/index.js:196:76) at Array.map (<anonymous>) at Object.<anonymous> (/usr/local/lib/node_modules/selenium-side-runner/dist/index.js:196:43) at Module._compile (module.js:652:30) at Object.Module._extensions…js (module.js:663:10) at Module.load (module.js:565:32) at tryModuleLoad (module.js:505:12) `

Is there something I am doing wrong? Or is it a bug in selenium-side-runner?

Actual Behavior -

Steps to reproduce -

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 17 (7 by maintainers)

Most upvoted comments

This seems like a problem with the container’s java setup rather than the runner, from a quick look it seems like a faulty installation of jre.

I think that your mount is incorrect, you mount a directory not a file, try mounting a directory containing the side file to the container’s home directory.
The permissions inside /tmp are sticky!
EDIT: docker run -v /path/to/directory_containing_side_files:/tests