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
Hi everyone,
I'm a newbie to docker, and I've tried running my tests on docker local container with not much success. I've wen't through this documentation: https://github.com/microsoft/playwright/tree/master/docs/docker
And got to this point: pwuser@c5275aa66a9d:/$
I've tried running npm run test command, but got this:
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pwuser/.npm/_logs/2020-04-24T23_45_48_490Z-debug.log
Of course I have a package.json script in the docker image (or at least in the folder I used to create the docker image from)
Thank you all for your kind help (I love playwright BTW!)
The text was updated successfully, but these errors were encountered:
barakbs1
changed the title
Help please [Question]
Playwright-Docker Help please [Question]
Apr 24, 2020
barakbs1
changed the title
Playwright-Docker Help please [Question]
Playwright-Docker help needed [Question]
Apr 24, 2020
barakbs1
changed the title
Playwright-Docker help needed [Question]
[Question] Playwright-Docker help needed
Apr 25, 2020
Hi everyone,
I'm a newbie to docker, and I've tried running my tests on docker local container with not much success. I've wen't through this documentation: https://github.com/microsoft/playwright/tree/master/docs/docker
And got to this point:
pwuser@c5275aa66a9d:/$
I've tried running
npm run test
command, but got this:Of course I have a package.json script in the docker image (or at least in the folder I used to create the docker image from)
Thank you all for your kind help (I love playwright BTW!)
The text was updated successfully, but these errors were encountered: