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
{{ message }}
This repository has been archived by the owner on Jan 15, 2023. It is now read-only.
I've been using alpine-node for a bit and find it useful (and minimal). Great base image. In the readme, you mention:
As Alpine Linux uses musl, you may run into some issues with environments expecting glibc-like behavior – especially if you try to use binaries compiled with glibc. You should recompile these binaries to use musl (compiling on Alpine is probably the easiest way to do this).
Are there any notable/common problem areas surrounding this? So far I've read that one such example is OracleJDK 8. Are there any other common libraries (for node use-cases) that require glibc? If so, can they be fully worked-around by compiling them against musl-libc? Are there any observed instances where this caveat cannot be worked around?
The text was updated successfully, but these errors were encountered:
Whereas in an ideal world, companies/ppl would provide binaries prebuilt for both systems, eg: https://zeit.co/download#command-line (now-linuxandnow-alpine)
I've been using alpine-node for a bit and find it useful (and minimal). Great base image. In the readme, you mention:
Are there any notable/common problem areas surrounding this? So far I've read that one such example is OracleJDK 8. Are there any other common libraries (for node use-cases) that require glibc? If so, can they be fully worked-around by compiling them against musl-libc? Are there any observed instances where this caveat cannot be worked around?
The text was updated successfully, but these errors were encountered: