sdkman-cli-native: Bug: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found

Bug report

just updated sdkman via cli today (2023-06-08) and now get the following error:

/****/.sdkman/libexec/help: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /****/.sdkman/libexec/help)

To reproduce

On Linux Mint 19.3 install/update sdkman

System info

$ uname -a
Linux oni 5.4.0-146-generic sdkman/sdkman-cli#163~18.04.1-Ubuntu SMP Mon Mar 20 15:02:59 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: LinuxMint
Description:    Linux Mint 19.3 Tricia
Release:        19.3
Codename:       tricia

$ sdk version
/home/fredo/.sdkman/libexec/version: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /home/fredo/.sdkman/libexec/version)

$ cat /****/.sdkman/var/version
5.18.1

$ cat /****/.sdkman/var/version_native 
0.1.3

Resolution Proposal

do a static link of your binaries against musl to make them distro/version agnostic.

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Comments: 19 (6 by maintainers)

Most upvoted comments

UPDATE: I looked at more alternatives and spun up a new self-hosted github runner for SDKMAN. The runner is a Centos 7 droplet on DigitalOcean (Amazon 1 is based on Centos 7 and has GLIB 2.17). I’ve performed a release of 0.4.0 of the native distribution, and everything seems to be working great in Docker.

@michelzanini could I please ask you to confirm if that works for you now?

@terefang also, please confirm that it solves your problem and feel free to close this issue if it does.

I have tested with the latest version and its working fine on Amazon Linux 2. Thanks!

UPDATE: I looked at more alternatives and spun up a new self-hosted github runner for SDKMAN. The runner is a Centos 7 droplet on DigitalOcean (Amazon 1 is based on Centos 7 and has GLIB 2.17). I’ve performed a release of 0.4.0 of the native distribution, and everything seems to be working great in Docker.

@michelzanini could I please ask you to confirm if that works for you now?

@terefang also, please confirm that it solves your problem and feel free to close this issue if it does.