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
As it turns out, the binaries we've built with wasm enabled (starting from 0.29.0) depend on glibc, but also have a minimum requirement: 2.18. As far as I can tell, that comes in from the version of glibc present in the host system used when building the binary -- in our case, that's the golang docker image.
The problem is Centos 7 (EOL 2024, still alive for a bit), which has an older version and no easy way to upgrade.
The workaround for now would be to use the static linux binaries on Centos 7, if you can work without the embedded wasm engine. If you need the wasm engine on Centos 7, you'd have to build the binary yourself on that system. (There's no known reason what that should be impossible.)
The text was updated successfully, but these errors were encountered:
Follow-up to #3499.
As it turns out, the binaries we've built with wasm enabled (starting from 0.29.0) depend on glibc, but also have a minimum requirement: 2.18. As far as I can tell, that comes in from the version of glibc present in the host system used when building the binary -- in our case, that's the golang docker image.
The problem is Centos 7 (EOL 2024, still alive for a bit), which has an older version and no easy way to upgrade.
The workaround for now would be to use the static linux binaries on Centos 7, if you can work without the embedded wasm engine. If you need the wasm engine on Centos 7, you'd have to build the binary yourself on that system. (There's no known reason what that should be impossible.)
The text was updated successfully, but these errors were encountered: