Please consider reverting AppImages to be built on 18.04

[Novum]

Or update the glibc version notice in the release docs. Building AppImages on 20.04 or 22.04 will produce binaries that require significantly newer Linux versions and I honestly do not understand what the upside is.

[vsonnier]

Hi @Novum I've read your other note also. There is no rush to take a recent distrib as base indeed. Going back to 18.04 will need to revert part of e8cf9ed, but right now I reverted 20.04 => 22.04.

[j4reporting]

There is no 18.04 docker image available anymore. It has been removed.

20.04 is the oldest available image on all ubuntu runners

https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2004-Readme.md
https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md

[vsonnier]

I should have made a branch for this sorry for the spam :)

Ubuntu 20.04 has glibc 2.31 apparently, so we should update the Releases description.

[vsonnier]

Updated Releases 1.31.x descriptions to specify 'at least 2.31'.

[bubbleguuum]

You can compile for an older version of the glibc with glibc_version_header. For example you can target v2.27 (Ubuntu 18.04) or older. I've used this to compile a static version of ffmpeg except for the glibc requiring v2.22+.

[Novum]

It's honestly crazy that the toolchain is so tightly tied to the system version on Linux, it always irritated me.

[bubbleguuum]

Agreed. The should be an easy way to configure gcc or clang to target any older version of the glibc.