GLIBC_2.32 not found when running under Ubuntu 20.04.6

[kalinkrustev]

Getting this:

[Error - 1:44:15 PM] The LLM VS Code server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
/home/user/.vscode-server/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/user/.vscode-server/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls)
/home/user/.vscode-server/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/user/.vscode-server/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls)
/home/user/.vscode-server/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/user/.vscode-server/extensions/huggingface.huggingface-vscode-0.1.0-linux-x64/server/llm-ls)

[McPatate]

Does running the following help:

apt update && apt install libc6

?

[kalinkrustev]

Not really. It returned:

libc6 is already the newest version (2.31-0ubuntu9.9).

I am not aware how Rust works, but when searching for this error, I found this golang/go#58550
Is there an equivalent for static linking (like CGO_ENABLED=0) in Rust?

[McPatate]

Well, I guess the solution would be to build on ubuntu 20.04. I've had issues setting up the build CI and I won't be taking a look at this in the short term, I have too many things to do 😅
If someone wants to give it a go, you can play around with the workflows in .github, my inspiration came from https://github.com/rust-lang/rust-analyzer.

For now the best workaround would be to compile llm-ls yourself, which shouldn't be too hard:

1. clone the repo & cd into it
2. install rust
3. cargo build --release

You may encounter some odd compile time errors.

[kalinkrustev]

There is no need to build on Ubuntu 20.04. The build target should be x86_64-unknown-linux-musl for static linking. I did some experiments and the produced binary runs fine with this target. The bad thing is that for this target name, the build happens under Alpine and produces an Alpine binary, which overwrites the same one built on Ubuntu. Maybe some change on the binary names could help, so that musl target is released for both Alpine and Ubuntu. I am not sure if x86_64-unknown-linux-gnu has any advantage over x86_64-unknown-linux-musl.

[cmosguy]

We are dealing with this is issue on our Cent OS 8 system.

ldd --version
ldd (GNU libc) 2.17

What is the solution to this so far? We really have to compile for older version of GLIBC?

[McPatate]

What is the solution to this so far? We really have to compile for older version of GLIBC?

For the time being yes. You can configure the llm-ls' binary path in every extension, let me know if you're having issues.

[cmosguy]

@McPatate thank you for your time and reply. Can you please send me a doc so that I can compile it on our systems? I know how to run make commands, but I am unsure how to drive the compilation with the cargo systems.

Thank you!

[kalinkrustev]

We are dealing with this is issue on our Cent OS 8 system.

ldd --version
ldd (GNU libc) 2.17

What is the solution to this so far? We really have to compile for older version of GLIBC?

Check my fork, where I disabled the Alpine build and instead released the Ubuntu binary with statically linked GLIBC. Check the released asset llm-ls-x86_64-unknown-linux-musl.gz, it should be usable under older Ubuntu and others.

[McPatate]

@cmosguy let me know if @kalinkrustev's binary works on your platform.

Otherwise it should be as simple as running the command provided here: https://www.rust-lang.org/tools/install & running cargo build in llm-ls' directory.

@kalinkrustev want to submit a PR to add the musl build in the release CI? This way we can redirect people on ubuntu that have incompatible GLIBC versions to download it (which at least skips the step of having to build it).