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
Steps to reproduce, I run next commands(tried Windows Command Prompt and Windows Powershell):
npm i backstopjs -g
backstopjs init
backstopjs test
backstopjs approve
backstop test --docker
Expected result:
The test should be executed in the same way as on step 3 Actual result:
BackstopJS v5.1.0
Loading config: C:\Source\backstopJSRunner\backstop.json
COMMAND | Executing core for "test"
Delegating command to Docker... docker run --rm -it --mount type=bind,source="C:\Source\backstopJSRunner",target=/src backstopjs/backstopjs:5.1.0 test "--moby"
docker: Error response from daemon: invalid mount config for type "bind": invalid mount path: '/src'.
See 'docker run --help'.
COMMAND | Executing core for "openReport"
openReport | Attempting to ping
COMMAND | Command "test" ended with an error after [1.847s]
COMMAND | Error: docker run --rm -it --mount type=bind,source="C:\Source\backstopJSRunner",target=/src backstopjs/backstopjs:5.1.0 test "--moby" returned 125
at ChildProcess.<anonymous> (C:\Users\Anton\AppData\Roaming\nvm\v12.18.3\node_modules\backstopjs\core\util\runDocker.js:68:18)
at ChildProcess.emit (events.js:315:20)
at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
openReport | Remote not detected. Opening backstop_data\html_report\index.html
C:\Source\backstopJSRunner>docker run --rm -it --mount type=bind,source="C:\Source\backstopJSRunner",target=/src backstopjs/backstopjs:5.1.0 test "--moby"
docker: Error response from daemon: invalid mount config for type "bind": invalid mount path: '/src'.
See 'docker run --help'.
The text was updated successfully, but these errors were encountered:
Steps to reproduce, I run next commands(tried Windows Command Prompt and Windows Powershell):
npm i backstopjs -g
backstopjs init
backstopjs test
backstopjs approve
backstop test --docker
Expected result:
The test should be executed in the same way as on step 3
Actual result:
The text was updated successfully, but these errors were encountered: