-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[BUG] version `GLIBC_2.18' not found while launching Chromium, with v1.15.0 #9194
Comments
@gkushang first of all, disclaimer: we don't officially support centOS – so it's all "best effort" here. Now, it might be that Chromium changed something upstream, or it might be some change in our infrastructure. To validate, can you please try downloading and running roughly the same Chromium build on CentOS? wget https://storage.googleapis.com/chromium-browser-snapshots/Linux_x64/920625/chrome-linux.zip |
I am also facing the same issue on our jenkins CI with similar configurations as mentioned above. |
@udit0802 please try downloading & running the chromium build on this configuration: wget https://storage.googleapis.com/chromium-browser-snapshots/Linux_x64/920625/chrome-linux.zip |
Could you please guide with the steps, are any changes required in the configuration of playwright from my end, or do you want me install manually this zip on centos machine? |
OK I already checked it in the Docker's centos:centos7 image. Turns out Chromium bumped it's GLIBC revision; I bisected it down to this range: https://chromium.googlesource.com/chromium/src/+log/08c30cf9e1370433a06980161e2b754c4b903e98..f61b6ea07f5050320e886b862379fdc8e36b3286 Anyway, there are no plans to support CentOS right now; if you'd like one, please file a separate issue requesting CentOS! If it gets lots of demand, we'll prioritize it! |
Is this issue also comes in windows agent in Jenkins |
As mentioned Chromium seemed to bump the this the middle of 2001. I was able to install a version that predates this on an older version of Centos that does not require glib later than 2.17 e.g. pip install --force-reinstall -v playwright==v1.10.0 |
playwright 1.10 is missing loads of features. For me I was able to get the features I wanted on CentOS 7 by installing with a later version As mentioned I previously tried to install the latest version (1.44.0) I also received When downloading a version (after x and before y) I get the following when using
If I understand correctly it is downloading the Ubuntu version of the build. 1.30 was working for me. Somewhere between 1.30 and 1.44 the installation breaks, specifically "version I believe there are workarounds to enable GLIBC_2.27 or later, but reading other comments, if you are not sure what you are doing, could lead to your server being unable to start. Not sure, but not something I really understand the implications of. |
Context:
Describe the bug
The issue started happening when we upgraded Playwright from
1.11.1
to1.15.0
. It does not launch thechromium
browser and throws an error,When I switch back to
v.1.11.1
, everything works fine butv1.15.0
needsGLIBC_2.18
on CentOS7. This is blocking us from upgrading.Playwright Slack Thread with @pavelfeldman
How do we resolve this issue?
The text was updated successfully, but these errors were encountered: