[1.0.1] Installer no longer works on major Linux distros (glibc)

[puttehi]

Looks like you have upgraded libc to 2.38+

$ curl -sSf https://install.spacetimedb.com > spacetime.sh
$ cat spacetime.sh # Reading through...
$ chmod u+x spacetime.sh
$ ./spacetime.sh
Downloading installer...
/tmp/tmp.baD0H7OmNq/spacetime-install: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/tmp.baD0H7OmNq/spacetime-install)

$ ldd --version
ldd (Ubuntu GLIBC 2.35-0ubuntu3.8) 2.35
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

Is there any valid reason to do this, or would it be possible to support LTS distros as well?

In this case:

$ uname -a
Linux myhostname 6.9.3-76060903-generic #202405300957~1736980680~22.04~44ea8a9 SMP PREEMPT_DYNAMIC Thu J x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Pop
Description:	Pop!_OS 22.04 LTS
Release:	22.04
Codename:	jammy

There is probably a nice compatibility chart online, but here's an idea of a support matrix:

Distro	glibc version
Arch Linux	2.40
Debian Stable	2.36
Fedora 40	2.39
Linux Mint 20	2.31
Linux Mint 21	2.35
Linux Mint 22	2.39
Linux Mint Debian Edition	2.36
Nix	2.39
OpenSuse Tumbleweed	2.40
Ubuntu 20.04	2.31
Ubuntu 22.04	2.35
Ubuntu 24.04	2.39
Void Linux	2.39

(From https://github.com/Detanup01/gbe_fork/issues/13)

[puttehi]

Thinking aloud; Should this be considered a breaking change in terms of semver? It does not run anymore, but it's also the installer that does not run, not necessarily the tech (that now cannot be accessed on the same system that the previous version could) 🤔

[bfops]

Thank you for reporting this! We'll triage this and investigate.

[clauses3]

Looks like 1.1.0 fixes this issue. It installs for me now.

[bfops]

Excellent! @puttehi is that true for you, too?

[bfops]

I'm going to close this issue. Please reopen if it's still causing problems.