-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found #221
Comments
Thanks for filing this. I think I know the issue. For node v23, they've made C++20 mandatory for addons, and we updated our toolchain to compile with that standard. We do compile the prebuilt binaries statically to avoid these issues, but glibc is still always dynamically linked because of how it is. At least for now, I don't see an easy workaround (besides using bookworm rather than bullseye, which I'm guessing isn't a simple change, or updating the libc version within docker, which is also challenging). For the next release, I'll see what I can do about this. Maybe revert the <22 node versions compilation to our older toolchain. |
I'm having the exact issue with |
@fadi-quader-mox , this issue shouldn't come for the alpine image since the build process for that isn't changed (and they don't use glibc). For me I get this:
Could you attach your logs for the alpine case? |
@milindl I use circleci It seems the circleci node image uses
so running that image on the Kubernetes cluster fails with this error
|
@fadi-quader-mox , this is a different issue, please see #48 . TL;DR, the binary of the wrong architecture/libc/OS gets copied into the docker container. To prevent this, in the Dockerfile, delete |
I had this exact error building on a clean node:18.14.0 docker image, any variant. I just tried bumping to node:23-alpine3.20 and am not seeing this load error anymore. |
@mattfiocca , 18.14.0 is based on bullseye as well, so for 1.0.0, it'll give the same issue. If you use something like 18.19.0 (based on bookworm), it should work. However, we do plan to fix this. |
Environment Information
node:18.17.0-bullseye-slim
Steps to Reproduce
Create this dockerfile:
Then run a docker build:
confluent-kafka-javascript Configuration Settings: N/A
Additional context: I guess 0.5.1 -> 1.0.0 is a breaking change after all
The text was updated successfully, but these errors were encountered: