-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run on non-Ubuntu linux distros? #61
Comments
Note: It is not a good practice, but it works in Playwright. The best practice is to go to the official repository, download the same version, and compile it on your distribution. However, there is something that some people do to run using different versions of libraries. I did it and, so far, I haven't had any compatibility problems. Basically, you need to create symbolic links to your libraries. First, you run Something like this will appear, then just run for the first item on the line: find /usr/lib64/ -name "libpcre.so*" The result may look like this: Then you just need to create the symbolic link: sudo ln -s /usr/lib64/libpcre.so.1 /usr/lib64/libpcre.so.3 Do this for each dependency and, in the end, run Another, easier way is to use Distrobox. It works in a container and is integrated with your folders and graphic server (Wayland or X11). You will use it as a Debian subsystem integrated with your machine. For more information, visit Distrobox. |
Thank you for the info @maxsonaraujo . There are times though that we don't have control over the server that we are running on. That I think is the opportunity something like a dev service could play here. A container that runs beside the app at test time, rather than on the host machine itself. |
@all-contributors add @edeandrea for idea |
I've put up a pull request to add @edeandrea! 🎉 |
@all-contributors add @maxsonaraujo for idea |
I've put up a pull request to add @maxsonaraujo! 🎉 |
It seems that for Linux, Playwright only works on Ubuntu distros (see microsoft/playwright#29559 & microsoft/playwright#19458).
It seems there is somewhat of a workaround to run the Playwright server in Docker (microsoft/playwright#26482).
Is there a way to get this to work with the extension? Maybe introducing a dev service rather than assuming that playwright will run on the host machine?
The text was updated successfully, but these errors were encountered: