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
Since we depend on a shim c layer differences in GLIBC versions may matter if build and runtime environments are different enough. This may result in errors akin to the following.
./demo_socket_listen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./demo_socket_listen)
./demo_socket_listen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./demo_socket_listen)
./demo_socket_listen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./demo_socket_listen)
If app deployment is containerized it shouldn't matter as the user controls libc version. Still calling this out explicitly wont hurt.
The text was updated successfully, but these errors were encountered:
Since we depend on a shim c layer differences in GLIBC versions may matter if build and runtime environments are different enough. This may result in errors akin to the following.
If app deployment is containerized it shouldn't matter as the user controls libc version. Still calling this out explicitly wont hurt.
The text was updated successfully, but these errors were encountered: