feat(ci): build with earlier version of GLIBC

[fuyufjh]

Got errors when I tried to run RisingWave on my EC2 machine.

[ec2-user@ip-172-31-11-6 risingwave]$ ./risingwave
./risingwave: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by ./risingwave)
./risingwave: /lib64/libm.so.6: version `GLIBC_2.29' not found (required by ./risingwave)
./risingwave: /lib64/libc.so.6: version `GLIBC_2.29' not found (required by ./risingwave)
./risingwave: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ./risingwave)
./risingwave: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./risingwave)
./risingwave: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by ./risingwave)
./risingwave: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by ./risingwave)

The OS is the latest version of Amazon Linux, which is the default option recommended by AWS. The GLIBC version shipped with OS is 2.26.

According to this article, the solution is to build RisingWave on a earlier Linux distribution (therefore with earlier version GLIBC)

container: quay.io/pypa/manylinux2014_x86_64

We may take a try.

[skyzh]

Or we can use musl instead of glibc?

[BugenZhao]

Or we can use musl instead of glibc?

How does musl performs compared to libc now?

[skyzh]

No idea :(

[fuyufjh]

I also had some concerns about the performance of musl. Earlier version GLIBC seems a better choice and it's adopted by Python officially.

[gitccl]

Same problem on ubuntu20.04.

./risingwave: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./risingwave)
./risingwave: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by ./risingwave)
./risingwave: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by ./risingwave)

[fuyufjh]

@huangjw806 any updates?

[huangjw806]

It has been solved, and the packages after v0.1.11 should be able to run normally on the above machines.