[QUESTION] `failed to launch chromium` error while running `npx jest` within Dockerfile.bionic #4485

fasatrix · 2020-11-19T04:17:06Z

Context:
I am using this container
https://github.com/microsoft/playwright/blob/master/docs/docker/Dockerfile.bionic

After running the container, install all dependencies successfully, I have the following error:

Command used to run the container:

docker run -it --name playwright  -v "C:\myProject\web":/home mcr.microsoft.com/playwright bash

Command used to install project dependencies:

npm install

Command to run tests:

npx jest

Error:

root@f542143afa64:/home/e2e_tests# npm run test

[email protected] test /home/e2e_tests
npx jest

Error: Failed to launch chromium because executable doesn't exist at /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome
Try re-installing playwright with "npm install playwright"
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.
    at Chromium._launchProcess (/home/e2e_tests/node_modules/playwright/lib/server/browserType.js:128:19)
    at async Chromium._innerLaunch (/home/e2e_tests/node_modules/playwright/lib/server/browserType.js:70:62)
    at async ProgressController.run (/home/e2e_tests/node_modules/playwright/lib/server/progress.js:85:28)
    at async Chromium.launch (/home/e2e_tests/node_modules/playwright/lib/server/browserType.js:53:25)
    at async BrowserServerLauncherImpl.launchServer (/home/e2e_tests/node_modules/playwright/lib/browserServerImpl.js:35:25)
    at async PlaywrightRunner.launchServer (/home/e2e_tests/node_modules/jest-playwright-preset/lib/PlaywrightRunner.js:61:48)
    at async PlaywrightRunner.getTests (/home/e2e_tests/node_modules/jest-playwright-preset/lib/PlaywrightRunner.js:96:40)
    at async PlaywrightRunner.runTests (/home/e2e_tests/node_modules/jest-playwright-preset/lib/PlaywrightRunner.js:123:30)
    at async TestScheduler.scheduleTests (/home/e2e_tests/node_modules/@jest/core/build/TestScheduler.js:321:13)
    at async runJest (/home/e2e_tests/node_modules/@jest/core/build/runJest.js:376:19)

Any idea to what is going wrong here? thx

my package.json

{
  "name": "catalogue-testing-framework-with-playwright",
  "version": "1.0.0",
  "description": " E2E testing framework",
  "main": "index.js",
  "scripts": {
    "lint": "eslint test/**/*.{js,ts,tsx} --quiet --fix",
    "pretty": "npx prettier --no-config test/**/*.{js,ts,tsx} --write",
    "test": "npx jest"
  },
  "dependencies": {
    "chromedriver": "85.0.1",
    "jest": "26.6.3",
    "jest-playwright": "0.0.1",
    "jest-playwright-preset": "^1.4.0",
    "playwright": "^1.5.2",
    "ts-jest": "26.4.4",
    "typescript": "4.0.5"
  },
  "devDependencies": {
    "@types/jest": "26.0.15",
    "@types/node": "13.13.30",
    "eslint": "^6.6.0",
    "expect-playwright": "^0.2.6",
    "jest-circus": "^26.6.3",
    "jest-html-reporters": "^2.1.0",
    "playwright-core": "^1.5.2",
    "prettier": "2.1.2"
  },
  "license": "MIT",
}

The text was updated successfully, but these errors were encountered:

golfzaptw · 2020-11-19T07:08:02Z

I got the same issue when I used the docker with the new Playwright version

pavelfeldman · 2020-11-19T16:48:16Z

My understanding is that npx does not run under root in docker and the temporary workaround is to npm i jest prior to calling it.

fasatrix · 2020-11-19T17:31:39Z

Thanks for your answer but still did not make much difference:

root@2af26501fb5b:/home/e2e_tests# **node_modules/jest/bin/jest.js test/**
Error: Failed to launch chromium because executable doesn't exist at /root/.cache/ms-playwright/chromium-827102/chrome-linux/chrome
Try re-installing playwright with "npm install playwright"
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.
    at Chromium._launchProcess (/home/e2e_tests/node_modules/playwright/lib/server/browserType.js:128:19)
    at async Chromium._innerLaunch (/home/e2e_tests/node_modules/playwright/lib/server/browserType.js:70:62)
    at async ProgressController.run (/home/e2e_tests/node_modules/playwright/lib/server/progress.js:85:28)
    at async Chromium.launch (/home/e2e_tests/node_modules/playwright/lib/server/browserType.js:53:25)
    at async BrowserServerLauncherImpl.launchServer (/home/e2e_tests/node_modules/playwright/lib/browserServerImpl.js:35:25)
    at async PlaywrightRunner.launchServer (/home/e2e_tests/node_modules/jest-playwright-preset/lib/PlaywrightRunner.js:61:48)
    at async PlaywrightRunner.getTests (/home/e2e_tests/node_modules/jest-playwright-preset/lib/PlaywrightRunner.js:96:40)
    at async PlaywrightRunner.runTests (/home/e2e_tests/node_modules/jest-playwright-preset/lib/PlaywrightRunner.js:123:30)
    at async TestScheduler.scheduleTests (/home/e2e_tests/node_modules/@jest/core/build/TestScheduler.js:321:13)
    at async runJest (/home/e2e_tests/node_modules/@jest/core/build/runJest.js:376:19)

Test Suites: 0 of 4 total
Tests: 0 total
Snapshots: 0 total
Time: 6 sroot@2af26501fb5b:/home/e2e_tests#

fasatrix · 2020-11-19T17:45:30Z

I have installed all packages with -g and getting the same error what I found as difference is that this time I have something under /root but chromium still missing

root@18d0b4236493:/home/e2e_tests # cd ~
root@18d0b4236493:~ # pwd
/root
root@18d0b4236493:~ # ls -la
total 40
drwx------ 1 root root 4096 Nov 17 21:06 .
drwxr-xr-x 1 root root 4096 Nov 19 17:34 ..
-rw-r--r-- 1 root root 3106 Apr 9 2018 .bashrc
drwxr-xr-x 2 root root 4096 Nov 17 21:06 .cache
drwx------ 1 root root 4096 Nov 17 21:06 .config
drwxr-xr-x 1 root root 4096 Nov 19 17:38 .npm
-rw-r--r-- 1 root root 148 Aug 17 2015 .profile
root@18d0b4236493:~ # ls .cache/ms-playwright
.cache/ms-playwright
root@18d0b4236493:~ # ls -ltr .cache/ms-playwright
lrwxrwxrwx 1 root root 34 Nov 17 21:06 .cache/ms-playwright -> /home/pwuser/.cache/ms-playwright/

fasatrix · 2020-11-19T18:41:15Z

hey I found the workaround but would be good to have it sorted for root too.

Entry point should be pwuser. then install all modules under that user (npm i) and voila'

pwuser@d35208e019fa:~/e2e_tests$ npm i
npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see request/request#3142
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated

[email protected] install /home/pwuser/e2e_tests/node_modules/playwright-core
node install.js

[email protected] install /home/pwuser/e2e_tests/node_modules/chromedriver
node install.js

/tmp/85.0.4183.87/chromedriver is not writable: EACCES: permission denied, open '/tmp/85.0.4183.87/chromedriver/1605810948234.tmp'
/tmp/85.0.4183.87/chromedriver is not writable: EACCES: permission denied, open '/tmp/85.0.4183.87/chromedriver/1605810948234.tmp'
Current existing ChromeDriver binary is unavailable, proceeding with download and extraction.
Downloading from file: https://chromedriver.storage.googleapis.com/85.0.4183.87/chromedriver_linux64.zip
Saving to file: /home/pwuser/e2e_tests/node_modules/chromedriver/tmp/85.0.4183.87/chromedriver/chromedriver_linux64.zip
Received 1040K...
Received 2080K...
Received 3120K...
Received 4160K...
Received 5200K...
Received 5233K total.
Extracting zip contents to /home/pwuser/e2e_tests/node_modules/chromedriver/tmp/85.0.4183.87/chromedriver.
Copying to target path /home/pwuser/e2e_tests/node_modules/chromedriver/lib/chromedriver
Fixing file permissions.
Done. ChromeDriver binary available at /home/pwuser/e2e_tests/node_modules/chromedriver/lib/chromedriver/chromedriver

[email protected] install /home/pwuser/e2e_tests/node_modules/playwright
node install.js

Downloading chromium v827102 - 119.8 Mb [====================] 100% 0.0s

chromium v827102 downloaded to /home/pwuser/.cache/ms-playwright/chromium-827102
Downloading firefox v1205 - 72.7 Mb [====================] 100% 0.0s
firefox v1205 downloaded to /home/pwuser/.cache/ms-playwright/firefox-1205
Downloading webkit v1383 - 71.3 Mb [====================] 100% 0.0s
webkit v1383 downloaded to /home/pwuser/.cache/ms-playwright/webkit-1383
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^2.1.2 (node_modules/jest-haste-map/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 751 packages from 472 contributors and audited 756 packages in 299.17s

31 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

pwuser@d35208e019fa:/e2e_tests$
pwuser@d35208e019fa:/e2e_tests$ ls -la /home/pwuser/.cache/ms-playwright/chromium-827102
total 0
drwxrwxr-x 1 pwuser pwuser 4096 Nov 19 18:37 .
drwxrwxr-x 1 pwuser pwuser 4096 Nov 19 18:37 ..
-rw-rw-r-- 1 pwuser pwuser 0 Nov 19 18:37 INSTALLATION_COMPLETE
drwxr-xr-x 1 pwuser pwuser 4096 Nov 19 18:37 chrome-linux

Prior99 · 2020-11-27T13:25:57Z

Same problem here. Seems like the image wasn't updated, but chrome was.

ryneeverett · 2020-12-16T14:38:33Z

TLDR Workaround: su pwuser

s2sa4v · 2020-12-22T23:25:17Z

Having the same issue. Running playwright with jest-playwright in Azure Pipelines inside a docker container. Tried suggested workarounds - did not help.

In my case, the npm install command downloads the chromium-833159 browser but the playwright looks for the chromium-827102.

Even if I set the browser path with executablePath option:

  launchOptions: {
    executablePath: '/home/pwuser/pw-browsers/chromium-833159/chrome-linux/chrome',
  },

it still looks for the chromium-827102 (but launches the chromium-833159 first?).

The logs that I'm getting with DEBUG=pw:browser:

 2020-12-22T21:53:48.907Z pw:browser <launching> /home/pwuser/pw-browsers/chromium-833159/chrome-linux/chrome --disable-background-networking --enable-features=NetworkService,NetworkServiceInProcess --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=TranslateUI,BlinkGenPropertyTrees,ImprovedCookieControls,SameSiteByDefaultCookies,LazyFrameLoading --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-sync --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --user-data-dir=/tmp/playwright_chromiumdev_profile-jkcTGS --remote-debugging-pipe --headless --hide-scrollbars --mute-audio --blink-settings=primaryHoverType=2,availableHoverTypes=2,primaryPointerType=4,availablePointerTypes=4 --no-sandbox --no-startup-window
 2020-12-22T21:53:48.913Z pw:browser <launched> pid=43
 2020-12-22T21:53:49.006Z pw:browser [err] [1222/215349.005503:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
 2020-12-22T21:53:53.237Z pw:browser [err] [1222/215349.021621:ERROR:vaapi_wrapper.cc(617)] Could not get a valid VA display
 FAIL browser: chromium specs/ux-landing-mocked.spec.ts
   ● website › Home
 
     browserType.launch: Failed to launch chromium because executable doesn't exist at /home/pwuser/pw-browsers/chromium-827102/chrome-linux/chrome
     Try re-installing playwright with "npm install playwright"
     Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.:

aslushnikov · 2021-02-01T22:09:36Z

(sorry for the long reply - we have a huge stream of incoming requests)

I am using this container
https://github.com/microsoft/playwright/blob/master/docs/docker/Dockerfile.bionic

@fasatrix did you just build it yourself and then use it? How would I reproduce this error locally?

aslushnikov · 2021-02-01T23:05:33Z

@alstas your case seems to be different. Can you please file a separate issue? Also, details that would help us reproduce this locally are greatly appreciated!

fasatrix · 2021-02-02T02:15:49Z

(sorry for the long reply - we have a huge stream of incoming requests)

I am using this container
https://github.com/microsoft/playwright/blob/master/docs/docker/Dockerfile.bionic

@fasatrix did you just build it yourself and then use it? How would I reproduce this error locally?

@aslushnikov No worries I know you guys are very busy..

I am using the following repo only as example but the behavior is exactly the same as for mine

Platform windows 10

Steps:

1. cd c:\temp (or wherever you want to)
2. git clone https://github.com/marcosvega91/msw-ssl.git
3. cd msw-ss
4. docker run -it --name playwright -v c:\temp\msw-ssl:/home mcr.microsoft.com/playwright bash
5. At this stage your prompt should be root
6. cd /home/src
7. npm install
8. npm run test

Error Outputted on screen

root@11675bad909f:/home# npm run test

> [email protected] test /home
> jest

Error: Failed to launch chromium because executable doesn't exist at /root/.cache/ms-playwright/chromium-844399/chrome-linux/chrome
Try re-installing playwright with "npm install playwright"
Note: use DEBUG=pw:api environment variable and rerun to capture Playwright logs.
    at Chromium._launchProcess (/home/node_modules/playwright/lib/server/browserType.js:134:19)
    at async Chromium._innerLaunch (/home/node_modules/playwright/lib/server/browserType.js:73:62)
    at async ProgressController.run (/home/node_modules/playwright/lib/server/progress.js:85:28)
    at async Chromium.launch (/home/node_modules/playwright/lib/server/browserType.js:55:25)
    at async BrowserServerLauncherImpl.launchServer (/home/node_modules/playwright/lib/browserServerImpl.js:35:25)
    at async PlaywrightRunner.launchServer (/home/node_modules/jest-playwright-preset/lib/PlaywrightRunner.js:62:48)
    at async PlaywrightRunner.getTests (/home/node_modules/jest-playwright-preset/lib/PlaywrightRunner.js:97:40)
    at async PlaywrightRunner.runTests (/home/node_modules/jest-playwright-preset/lib/PlaywrightRunner.js:121:30)
    at async TestScheduler.scheduleTests (/home/node_modules/@jest/core/build/TestScheduler.js:321:13)
    at async runJest (/home/node_modules/@jest/core/build/runJest.js:376:19)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] test: `jest`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-02-02T02_15_30_862Z-debug.log
root@11675bad909f:/home#

Where as if I do this:

1. cd c:\temp (or wherever you want to)
2. git clone https://github.com/marcosvega91/msw-ssl.git
3. cd msw-ss
4. docker run -it --name playwright --user pwuser -v c:\temp\msw-ssl:/home/pwuser mcr.microsoft.com/playwright bash
5. At this stage your prompt should be root
6.  cd /home/pwuser/
7. npm install
8. npm run test

I get this(basically chromium is found and test runs):

`$ npm i
npm WARN deprecated [email protected]: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi'
npm WARN deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-babel.
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address'
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see request/request#3142
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated [email protected]: this library is no longer supported

[email protected] install /home/pwuser/node_modules/jest-playwright-preset/node_modules/playwright-core
node install.js

[email protected] install /home/pwuser/node_modules/playwright
node install.js

Downloading chromium v844399 - 122 Mb [====================] 100% 0.0s

chromium v844399 downloaded to /home/pwuser/.cache/ms-playwright/chromium-844399
Downloading firefox v1225 - 72.2 Mb [====================] 100% 0.0s
firefox v1225 downloaded to /home/pwuser/.cache/ms-playwright/firefox-1225
Downloading webkit v1423 - 76.8 Mb [====================] 100% 0.0s
webkit v1423 downloaded to /home/pwuser/.cache/ms-playwright/webkit-1423

[email protected] postinstall /home/pwuser/node_modules/babel-runtime/node_modules/core-js
node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:

https://opencollective.com/core-js
https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

[email protected] postinstall /home/pwuser/node_modules/core-js
node -e "try{require('./postinstall')}catch(e){}"

[email protected] postinstall /home/pwuser/node_modules/core-js-pure
node -e "try{require('./postinstall')}catch(e){}"

[email protected] postinstall /home/pwuser/node_modules/ejs
node ./postinstall.js

Thank you for installing EJS: built with the Jake JavaScript build tool (https://jakejs.com/)

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/webpack-dev-server/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN [email protected] requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of playwright-core@^1.8.0 but none is installed. You must install peer dependencies yourself.

added 1958 packages from 805 contributors and audited 1961 packages in 442.996s

129 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

pwuser@1ef095526b87:$
pwuser@1ef095526b87:$
pwuser@1ef095526b87:~$ npm run test

[email protected] test /home/pwuser
jest

FAIL browser: chromium src/tests/App.js (29.881 s)`

fasatrix · 2021-02-02T02:20:49Z

@aslushnikov
on a different note where would it be a good place to start a conversation around playwright and openlayers (https://openlayers.org/) testing?
My team is building apps that are using openlayers as base for maps and build the application on top of that (layers). We would like to use some playwright APIs to interact with openlayers (e.g zoom in , draws polygons , select points etc.)
I was able to do some very basic interaction using puppeteer using but not totally satisfied .. however it seems harder with playwright.. Do you guys have any suggestion/recommendation to tests map with playwright?

aslushnikov · 2021-02-12T01:03:38Z

@fasatrix awesome, thank you for the repro. I can repro now.

docker run -it --name playwright --user pwuser -v c:\temp\msw-ssl:/home/pwuser mcr.microsoft.com/playwright bash

The reason this doesn't work is because you're overwriting the /home/pwuser location with your project mount. The /home/pwuser location contains playwright registry, so after this things go south.

One easy fix would be to mount your project to some root location inside docker. For example, the following worked for me:

$ docker run -it --name playwright --user pwuser -v c:\temp\msw-ssl:/mswssl mcr.microsoft.com/playwright bash
$ cd /mswssl
$ npm ci && npm run test

On a related note, I'd recommend using a docker image version that matches the playwright version you use. This way
you can save some time on npm i step inside docker since playwright will use the pre-installed browsers inside docker image.

Since you use playwright v1.6.2, you can use a matching docker image;

$ docker run -it --rm -v c:\temp\msw-ssl:/mswssl mcr.microsoft.com/playwright:v1.6.2 bash
$ cd /mswssl
$ npm ci && npm run test

on a different note where would it be a good place to start a conversation around playwright and openlayers (https://openlayers.org/) testing?

I'd suggest opening a new issue and sharing your problems. It should all just work!

Instead of symlinking pwuser's registry to root's registry, we now use the `PLAYWRIGHT_BROWSERS_PATH` variable to define a single browser registry across the docker image, accessible for all users. Fixes microsoft#4485

aslushnikov · 2021-02-12T02:21:25Z

@fasatrix but actually let me try fixing our docker image..

Instead of symlinking pwuser's registry to root's registry, we now use the `PLAYWRIGHT_BROWSERS_PATH` variable to define a single browser registry across the docker image, accessible for all users. Fixes #4485

fasatrix · 2021-02-12T05:34:03Z

@fasatrix but actually let me try fixing our docker image..

That's what I thought it'd be the best anti error prone solution. Thanks allot @aslushnikov you are the best 😉

nboisteault · 2022-04-15T15:02:17Z

@aslushnikov on a different note where would it be a good place to start a conversation around playwright and openlayers (https://openlayers.org/) testing? My team is building apps that are using openlayers as base for maps and build the application on top of that (layers). We would like to use some playwright APIs to interact with openlayers (e.g zoom in , draws polygons , select points etc.) I was able to do some very basic interaction using puppeteer using but not totally satisfied .. however it seems harder with playwright.. Do you guys have any suggestion/recommendation to tests map with playwright?

Hi @fasatrix I'm also interested in testing OpenLayers with Playwright. Did you achieve to draw a point and move it on the map with Playwright?

fasatrix changed the title ~~[BUG] failed to launch chromium error while running npx jest within Dockerfile.bionic~~ [QUESTION] failed to launch chromium error while running npx jest within Dockerfile.bionic Nov 19, 2020

pavelfeldman assigned aslushnikov Nov 19, 2020

pavelfeldman added the v1.7 label Nov 19, 2020

pavelfeldman added the P2-bug label Nov 19, 2020

pavelfeldman added v1.9 and removed v1.7 labels Jan 18, 2021

aslushnikov mentioned this issue Feb 12, 2021

fix(docker): avoid symlink hack in Docker images #5429

Merged

aslushnikov closed this as completed in #5429 Feb 12, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[QUESTION] `failed to launch chromium` error while running `npx jest` within Dockerfile.bionic #4485

[QUESTION] `failed to launch chromium` error while running `npx jest` within Dockerfile.bionic #4485

fasatrix commented Nov 19, 2020 •

edited by aslushnikov

Loading

golfzaptw commented Nov 19, 2020

pavelfeldman commented Nov 19, 2020

fasatrix commented Nov 19, 2020 •

edited by aslushnikov

Loading

fasatrix commented Nov 19, 2020 •

edited

Loading

fasatrix commented Nov 19, 2020

Prior99 commented Nov 27, 2020

ryneeverett commented Dec 16, 2020

s2sa4v commented Dec 22, 2020

aslushnikov commented Feb 1, 2021

aslushnikov commented Feb 1, 2021

fasatrix commented Feb 2, 2021 •

edited

Loading

fasatrix commented Feb 2, 2021 •

edited

Loading

aslushnikov commented Feb 12, 2021

aslushnikov commented Feb 12, 2021

fasatrix commented Feb 12, 2021

nboisteault commented Apr 15, 2022

[QUESTION] failed to launch chromium error while running npx jest within Dockerfile.bionic #4485

[QUESTION] failed to launch chromium error while running npx jest within Dockerfile.bionic #4485

Comments

fasatrix commented Nov 19, 2020 • edited by aslushnikov Loading

golfzaptw commented Nov 19, 2020

pavelfeldman commented Nov 19, 2020

fasatrix commented Nov 19, 2020 • edited by aslushnikov Loading

fasatrix commented Nov 19, 2020 • edited Loading

fasatrix commented Nov 19, 2020

Prior99 commented Nov 27, 2020

ryneeverett commented Dec 16, 2020

s2sa4v commented Dec 22, 2020

aslushnikov commented Feb 1, 2021

aslushnikov commented Feb 1, 2021

fasatrix commented Feb 2, 2021 • edited Loading

Platform windows 10

Steps:

Error Outputted on screen

Where as if I do this:

I get this(basically chromium is found and test runs):

fasatrix commented Feb 2, 2021 • edited Loading

aslushnikov commented Feb 12, 2021

aslushnikov commented Feb 12, 2021

fasatrix commented Feb 12, 2021

nboisteault commented Apr 15, 2022

[QUESTION] `failed to launch chromium` error while running `npx jest` within Dockerfile.bionic #4485

[QUESTION] `failed to launch chromium` error while running `npx jest` within Dockerfile.bionic #4485

fasatrix commented Nov 19, 2020 •

edited by aslushnikov

Loading

fasatrix commented Nov 19, 2020 •

edited by aslushnikov

Loading

fasatrix commented Nov 19, 2020 •

edited

Loading

fasatrix commented Feb 2, 2021 •

edited

Loading

fasatrix commented Feb 2, 2021 •

edited

Loading