glibc for Pharo 13 not found

[theseion]

Since a couple of weeks, SmalltalkCI builds for Pharo 13 no longer work due to the following error (SmalltalkCI uses zero-conf):

2024-11-02T04:46:25.2437109Z �[1m�[34mStarting Pharo build...�[0m
2024-11-02T04:46:25.2496420Z �[1m�[34mDownloading Pharo64-alpha image...�[0m
2024-11-02T04:46:25.6926140Z Downloading the latest 130 Image:
2024-11-02T04:46:25.6927310Z     http://files.pharo.org/get-files/130/pharoImage-x86_64.zip
2024-11-02T04:46:28.9059795Z Pharo.image
2024-11-02T04:46:28.9121633Z �[0m�[34m > Time to run: 3.660s�[0m
2024-11-02T04:46:28.9122425Z �[1m�[34mPreparing Pharo image...�[0m
2024-11-02T04:46:29.0223983Z �[1m�[34mDownloading Pharo64-alpha vm...�[0m
2024-11-02T04:46:29.3409532Z Downloading the latest pharoVM:
2024-11-02T04:46:29.3410865Z 	http://files.pharo.org/get-files/130/pharo-vm-Linux-x86_64-latest.zip
2024-11-02T04:46:35.4352643Z pharo-vm/pharo
2024-11-02T04:46:35.4353487Z Creating starter scripts pharo and pharo-ui
2024-11-02T04:46:35.4436873Z �[0m�[34m > Time to run: 6.419s�[0m
2024-11-02T04:46:35.4807879Z /home/runner/.smalltalkCI/_cache/vms/Pharo64-alpha/pharo-vm/lib/pharo: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/runner/.smalltalkCI/_cache/vms/Pharo64-alpha/pharo-vm/lib/pharo)
2024-11-02T04:46:35.4811628Z /home/runner/.smalltalkCI/_cache/vms/Pharo64-alpha/pharo-vm/lib/pharo: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/runner/.smalltalkCI/_cache/vms/Pharo64-alpha/pharo-vm/lib/libPharoVMCore.so)
2024-11-02T04:46:35.4815375Z /home/runner/.smalltalkCI/_cache/vms/Pharo64-alpha/pharo-vm/lib/pharo: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/runner/.smalltalkCI/_cache/vms/Pharo64-alpha/pharo-vm/lib/libPharoVMCore.so)
2024-11-02T04:46:35.4816594Z 
2024-11-02T04:46:35.4816811Z �[1m�[33mError with status code 1:�[0m
2024-11-02T04:46:35.4817301Z 712 run_script /home/runner/.smalltalkCI/helpers.sh
2024-11-02T04:46:36.0078011Z ##[error]Process completed with exit code 1.

[theseion]

@guillep

[theseion]

@MarcusDenker

[guillep]

Hi, @theseion , We changed the linux CI infrastructure a couple of weeks ago, probably using a newer ubuntu/debian is the cause behind this.

We are going to discuss about this.

Now, what runner is the SmalltalkCI using for linux? Bumping the runner to a newer version is maybe another solution.

[theseion]

It's Ubuntu 20.04. Would be nice to use ubuntu-latest :)