- Más nuevo
- Más votos
- Más comentarios
Hi,
If you look at Amazon Linux 2 FAQ at https://aws.amazon.com/amazon-linux-2/faqs/ you will see that its end of life was postponed from 2023 to June 2025.
Q. When will support for Amazon Linux 2 end?
Amazon Linux 2 end of support date (End of Life, or EOL) has been extended
by two years from 2023-06-30 to 2025-06-30 to provide customers with ample
time to migrate to the next version.
So, it is better to migrate to Linux 2023 if it doesn't represent too much effort since Chrome 127 works on it: you will anyway have to do it in less than a year now.
Best,
Didier
If I was on Airflow 2.4.3 using Amazon MWAA, would upgrading to 2.6.3 solve this issue? I couldn't find in the Airflow docs what versions of Airflow use Linux 2023
The error text is a bit hidden as yum
isn't knowing what to do, so we can look at rpm
itself. I've reproduced the relevant snippets below:
bash-4.2# rpm -ivh ./google-chrome-unstable-128.0.6613.7-1.x86_64.rpm
warning: ./google-chrome-unstable-128.0.6613.7-1.x86_64.rpm: Header V4 RSA/SHA512 Signature, key ID 9b30acf2: NOKEY
error: Failed dependencies:
(libcurl.so()(64bit) or libcurl-gnutls.so.4()(64bit) or libcurl-nss.so.4()(64bit) or libcurl.so.4()(64bit)) is needed by google-chrome-unstable-128.0.6613.7-1.x86_64
(libgtk-3.so.0()(64bit) or libgtk-4.so.1()(64bit)) is needed by google-chrome-unstable-128.0.6613.7-1.x86_64
.....
rpmlib(RichDependencies) <= 4.12.0-1 is needed by google-chrome-unstable-128.0.6613.7-1.x86_64
This is telling you (in a not entirely obvious way) that Google is using features in a newer version of rpm
than what is in Amazon Linux 2. The RichDependencies feature was introduced in rpm
v4.13, while AL2 has rpm
v4.11.
The yum
and dnf
package managers in AL2 and AL2023 respectively all sit on top of rpm
, and in this case the features being used by this particular RPM package would need to be supported in both rpm
and what sits above it (e.g. yum
).
AFAIK Google does not list Amazon Linux 2 as a supported platform for Chrome, and so it does appear that they are now relying on newer functionality than is available on AL2.
Contenido relevante
- OFICIAL DE AWSActualizada hace 2 años
- OFICIAL DE AWSActualizada hace 6 meses
- OFICIAL DE AWSActualizada hace 6 meses
- OFICIAL DE AWSActualizada hace 2 años
I am having the same issue but just yesterday Google Chrome couldn't be installed as you posted above. The only difference with my implementation is that I was Amazon MWAA for Airflow jobs and on Airflow version 2.4.3. I am scrambling now trying to fix this issue quickly and unsure how. I am attempting to upgrade to Airflow 2.6.3 so that i don't have to reconfigure my requirements file with the newer Airflow versions but just kinda scrambling here.