You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
Building and running a mostly static native image on Ubuntu 22.04 works fine, but when executing this same native image on Ubuntu 20.04, there seems to be a version incompatibility of GLibC. Both systems run on amd64.
Build a native image from this project (./gradlew nativeCompile) on an Ubuntu 22.04 machine
Execute this image on an Ubuntu 20.04 machine (e.g. in a Docker container)
Describe GraalVM and your environment:
GraalVM version: GraalVM CE 23.0.0-dev-20230303_0222
JDK major version: 17
OS: Ubuntu 22.04
Architecture: AMD64
More details
I have also checked that the issue is not related to the Gradle plugin but just provided an example with it for convenience.
The error output when executing on Ubuntu 20.04:
/app: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /app)
/app: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /app)
I couldn't find information regarding incompatibility between linux distros running different versions of GlibC. But that shouldn't be an issue, right?
The text was updated successfully, but these errors were encountered:
Describe the issue
Building and running a mostly static native image on Ubuntu 22.04 works fine, but when executing this same native image on Ubuntu 20.04, there seems to be a version incompatibility of GLibC. Both systems run on amd64.
Steps to reproduce the issue
./gradlew nativeCompile
) on an Ubuntu 22.04 machineDescribe GraalVM and your environment:
More details
I have also checked that the issue is not related to the Gradle plugin but just provided an example with it for convenience.
The error output when executing on Ubuntu 20.04:
I couldn't find information regarding incompatibility between linux distros running different versions of GlibC. But that shouldn't be an issue, right?
The text was updated successfully, but these errors were encountered: