Installation error due to GLIBC version while using automatic sprocket installation

[FHaggs]

I encountered an issue when attempting to use the Sprocket extension in Visual Studio Code. The extension fails to automatically install the sprocket command line tool due to an incompatible version of libc on my system. Below is the error message I received:

/home/pedro/.config/Code/User/globalStorage/stjude-rust-labs.sprocket-vscode/file-downloader-downloads/sprocket: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by /home/pedro/.config/Code/User/globalStorage/stjude-rust-labs.sprocket-vscode/file-downloader-downloads/sprocket)

Workaround: I manually compiled and installed the sprocket binary on my machine using the following steps:
Installed the latest version of sprocket using cargo install sprocket.
Replaced the binary in the extension's folder with the manually compiled version, and it worked as expected.

System Information:

OS: Debian GNU/Linux 12 (bookworm)
Rust version: rustc 1.85.0 (4d91de4e4 2025-02-17
GLIBC version: ldd (Debian GLIBC 2.36-9+deb12u10) 2.36
VSCode version: 1.98.2
Sprocket extension version: 0.3.0

[SanjayUG]

Hi there,

I would be helping you to sort out this error.

Feel free for Feedback.

[peterhuene]

Thanks for reporting this and thanks to @SanjayUG for the PR to help improve the user experience when folks run into this issue going forward.

We are hoping to produce a statically-linked ELF binary for the VS Code extension to use on Linux so that we don't run into these incompatible/missing shared objects in the future.

[dead8309]

We are hoping to produce a statically-linked ELF binary for the VS Code extension to use on Linux so that we don't run into these incompatible/missing shared objects in the future.

from slack: Also on the same topic many people are getting errors while installing the sprocket binary via the extension, other extensions like java intellisense or nodejs just redirect user to their extension page if they do not have their binary in path. Maybe we could also do that and redirect user to extension page with the installation steps clearly mentioned.
If sprocket had to support other editors/ides in future then we'll have to write the download script in their extension language (Java/Kotlin incase of IntelliJ) vs having a single instruction page for downloading/installing the binary