geth 1.14.6 requires newer glibc

[Crypto2]

It should be noted in the release notes that the official binary for geth requires a newer glibc

[alex2grad]

The Linux 64-bit pre-built binaries v1.14.6 require GLIBC_2.34.
The prev version required GLIBC_2.17.
The GNU C Library version 2.34 is less then 3 years old and many Linux distributions still have older versions of GLIBC.
It would be nice if we can download static linking pre-built binaries for Linux 64-bit.

[karalabe]

glibc cannot be statically linked, at least not in Go.

I guess the issue stems from us updating our builders to a newer Ubuntu version. (cc @holiman). Though tbh, I'm not sure what we can meaningfully do here. Using an old version of glibs is just as arbitrary as using a new one, isn't it?

[alex2grad]

The docker image ethereum/client-go:alltools-latest has statically linked binaries for Linux 64-bit

#file geth
geth: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=339b91232aaf970656908d202da063425d3f0fc6, with debug_info, not stripped

#ldd geth
not a dynamic executable

So the project already supports static linking.

[karalabe]

Yeah, but the docker executables run on alpine and use musl, not libc.

…

On Fri, 5 Jul 2024 at 23:59, alex2grad ***@***.***> wrote: The docker image ethereum/client-go:alltools-latest has statically linked binaries for Linux 64-bit #file geth geth: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=339b91232aaf970656908d202da063425d3f0fc6, with debug_info, not stripped ldd geth not a dynamic executable So the project already supports static linking. — Reply to this email directly, view it on GitHub <#30115 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA7UGLDDDOBKNPHNNMSZMDZK4CJZAVCNFSM6AAAAABKJZFBY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGQYDKOJWGA> . You are receiving this because you commented.Message ID: ***@***.***>

[alex2grad]

Static executables don't carry dynamic dependencies or libc version and could run on any Linux.

For example I run geth executable from docker image ethereum/client-go:alltools-v1.14.6
on Slackware 15.0 x86_64

#./geth --version
geth version 1.14.6-stable-aadddf3a

#./geth version-check
INFO [07-06|17:32:57.091] Checking vulnerabilities version=Geth/v1.14.6-stable-aadddf3a/linux-amd64/go1.22.4 url=https://geth.ethereum.org/docs/vulnerabilities/vulnerabilities.json
No vulnerabilities found

#uname -a
Linux alex-dev 6.6.36 #1 SMP Thu Jun 27 11:32:11 EDT 2024 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux

#cat /etc/os-release
NAME=Slackware
VERSION="15.0"
ID=slackware
VERSION_ID=15.0
PRETTY_NAME="Slackware 15.0 x86_64"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:slackware:slackware_linux:15.0"
HOME_URL="http://slackware.com/"
SUPPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"
BUG_REPORT_URL="http://www.linuxquestions.org/questions/slackware-14/"
VERSION_CODENAME=stable

[jcjc7777]

I had the same issue on the ARM64 binary. I am on 22.04 and don't know how to upgrade GLIBC to the version requested by geth so I will downgrade until I figure out how to upgrade or something is put in the release notes.

[Alleysira]

Same problem happens in Ubuntu-20.04 in wsl, it seems not solved yet.

/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found

[Neurone]

Same issue here with native Ubuntu 20.04 (full updated). Can this StackOverflow answer be the solution?

replace FROM go:1.21 with FROM go:1.21.0-bullseye

[agathakazar]

Ran into this on Debian 11 which has glibc 2.31, a release note would've been nice unless it's a bug

[trojan20161207]

I met this question,too. My ec2's linux system is AWS linux 2,and the glibc version is glibc-2.26-63.amzn2.0.1.x86_64.
When I use the v1.13.14 version is ok,so I have to rollout to v1.13.

[fjl]

Sorry, we kind of dropped the ball here and forgot about this issue in the last release. We didn't intentionally break compatibility with older glibc versions, so it could be classified as a bug. Let me summarize the affected distributions:

• Ubuntu 20.04
• Ubuntu 22.04
• Debian 11
• AWS Linux 2

For these distributions, the binary provided on geth.ethereum.org does not launch.

[fjl]

The issue has been investigated further, and returning to Ubuntu 18.04 Bionic on builders is not an option for us. Travis CI has deprecated this version and only supports Ubuntu 20.04 and 22.04 going forward. We will stick to Ubuntu 20.04 Focal, and this means we are bound to the glibc version provided by it.

The only other available option would be publishing fully static builds. It is possible to build Geth as a statically-linked executable, but we have not tested glibc in static mode. AFAIK it will still retain a reference to certain dynamic glibc modules within the binary even if glibc itself is linked in statically.

[fjl]

I actually wonder how it could be that our pre-built Geth binary, built on Ubuntu 20.04, does not launch on that same version of Ubuntu.