Hi everyone, is there any clue causing browserType.launchPersistentContext
in headless:false
failed with following errors? the app is running in Docker and launched with xvfb-run --auto-servernum --server-num=1 node ./built
errors: Please check the attached log file for chrome errors due to the length limitation, many thanks!
==================== Browser output: ====================
<launching> /ms-playwright/firefox-1391/firefox/firefox -no-remote -wait-for-browser -foreground -profile /tmp/playwright_firefoxdev_profile-BTIPhY -juggler-pipe about:blank
<launched> pid=130795
[pid=130795][err] Authorization required, but no authorization protocol specified
[pid=130795][err] Error: cannot open display: :1
[pid=130795] <process did exit: exitCode=1, signal=null>
[pid=130795] starting temporary directories cleanup
=========================== logs ===========================
<launching> /ms-playwright/firefox-1391/firefox/firefox -no-remote -wait-for-browser -foreground -profile /tmp/playwright_firefoxdev_profile-BTIPhY -juggler-pipe about:blank
<launched> pid=130795
[pid=130795][err] Authorization required, but no authorization protocol specified
[pid=130795][err] Error: cannot open display: :1
[pid=130795] <process did exit: exitCode=1, signal=null>
[pid=130795] starting temporary directories cleanup
This thread is trying to answer question "What could be causing `browserType.launchPersistentContext` to fail with authorization and display errors when running in a Docker container with `headless:false`?"
Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email [email protected].