chore: fix: ARM64 - Build Centos7 for sqlite3 dependency

[jsamuel1]

• Fixes `GLIBC_2.29' not found on Graviton ARM linux, when using Centos7 or RHEL8 base docker images #28525
• (Possibly also fixes GLIBC_2.29 not found when running in a docker container on a mac with m1 #28374 )

Additional details

This change builds the older dependency for sqlite3 on linux-arm64, such that docker containers on arm64 using RHEL7/8 or CENTOS7/8 won't get a glibc version error.

A conditional was added in the sqlite3 centos build, such that the build could proceed on machine workers as well as docker workers.

PR Tasks

• Have tests been added/updated? NA
• Has a PR for user-facing changes been opened in cypress-documentation? NA
• Have API changes been updated in the type definitions? NA

[CLAassistant]

All committers have signed the CLA.

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[jsamuel1]

Note - it may be beneficial to add a linux-arm64-contributor-workflow in the future, to ensure that ARM builds are tested in PR.

[astone123]

@jsamuel1 thanks for opening this. I think #28374 is a separate issue from this, both having to do with GLIBC.

Would you be willing to open a new issue describing what you're seeing related to the better sqlite GLIBC error on Linux ARM? That would help us keep these two issues separate and then we can move forward with testing this change. Thanks

[jsamuel1]

@astone123 Created issue #28525

[Younis-NAB]

Hi @astone123 , @jennifer-shehane

Is there any updates on this PR ?

[emilyrohrbough]

@jsamuel1 Thank you for opening a PR. I have reviewed the linked issue, and I’m not sure this change would fix this issue. This change would fix that error in our CI pipeline, but our CI does not release an image for other to consume. Our docker images are maintained and released in https://github.com/cypress-io/cypress-docker-images.

Is it possible this change should be made here instead? https://github.com/cypress-io/cypress-docker-images/blob/master/circle.yml

[jsamuel1]

@emilyrohrbough I’m looking to fix it for the install package, rather than a docker image, for people that build their own docker images.

Are your packages also published from the docker repository?

[emilyrohrbough]

@jsamuel1 No, you are correct the Cypress package is published from here.

[ryanthemanuel]

Hi @jsamuel1. The issue you are seeing with addon-native.node actually comes from our binary publishing process, which is not done in this repo. We’ll need to make a change there in order to fix this. Right now, that work is not currently scheduled.

[jsamuel1]

Hi @jsamuel1. The issue you are seeing with addon-native.node actually comes from our binary publishing process, which is not done in this repo. We’ll need to make a change there in order to fix this. Right now, that work is not currently scheduled.

Thanks Ryan. Anything I can do to help with the binary publishing fix, or is it in a private repo?

[jennifer-shehane]

@jsamuel1 It's in a private repo

[Younis-NAB]

Hey @ryanthemanuel @jennifer-shehane any timeline when the binary issue will be addressed ?

[jennifer-shehane]

@Younis-NAB Sorry, this is not on the list of prioritized work for us atm.

[cypress-app-bot]

This PR has not had any activity in 180 days. If no activity is detected in the next 14 days, this PR will be closed.