Skip to content
This repository has been archived by the owner on Jan 15, 2023. It is now read-only.

Specific examples where musl-libc can be problematic? #107

Closed
samlevin opened this issue Sep 25, 2017 · 3 comments
Closed

Specific examples where musl-libc can be problematic? #107

samlevin opened this issue Sep 25, 2017 · 3 comments

Comments

@samlevin
Copy link

samlevin commented Sep 25, 2017

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?

@mhart
Copy link
Owner

mhart commented Sep 25, 2017

It mostly affects things where there are prebuilt binaries that don't distinguish between glibc and musl – like for example https://www.npmjs.com/package/phantomjs-prebuilt

@mhart
Copy link
Owner

mhart commented Sep 25, 2017

Whereas in an ideal world, companies/ppl would provide binaries prebuilt for both systems, eg: https://zeit.co/download#command-line (now-linux and now-alpine)

@samlevin
Copy link
Author

Thanks for the info @mhart!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants