Am 09.12.24 um 20:29 schrieb Ruben Perez:
Does using ubuntu-latest as host OS and ubuntu 16.04 as container not work? Unfortunately not. Seems I forgot to mention this clarification:
The action will run inside the container with the Node binary mounted from the host OS. That Node (version 20) is built against a newer glibc than available inside the Ubuntu 16/18 container. So using the Node from an even newer OS makes the problem worse as it might have used/require an even newer glibc. Besides dropping those containers or the GitHub actions (used for checkouts with setting useful config params; coverage uploads and maybe more) the only solution is to use a Node 20 specifically built against a glibc supported by those containers. This is also done conditionally by using the mounts only when an ubuntu:1* container is detected and the download script also checks that condition which should avoid any side effects for recent-enough OS/containers.