Skip to content
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

Alpine Linux support #48

Open
langri-sha opened this issue Jun 18, 2018 · 6 comments
Open

Alpine Linux support #48

langri-sha opened this issue Jun 18, 2018 · 6 comments

Comments

@langri-sha
Copy link

I tried using this as a substitute for nvm and I'm really liking it!

It works nicely on my Arch Linux host, but I tried running this inside an Alpine Linux container and it seems the resolved binary doesn't seem to run.

image

@aredridel
Copy link
Owner

That looks a bit like the node interpreter doesn't run. What makes alpine special?

If you run ldd on that binary, what does it spit out?

@langri-sha
Copy link
Author

I think it's a bit special because it uses http://www.musl-libc.org/, here's the documentation.

I've looked at the official Node.js containers and they seem to build from sources. I'll try running ldd on the binary ASAP and give you the output.

@aredridel
Copy link
Owner

That makes sense, then. It doesn't run with the standard libraries, and it's not the node binaries from nodejs.org.

This package so far only provides official binaries. I'd be into adding unofficial ones if someone else wants to publish and maintain them, and a clean way to signal 'Unofficial binaries are okay' to the installer. Some sort of environment variable or package.json thing maybe?

@aredridel
Copy link
Owner

Or a 'use this flavor of unofficial binaries' -- like "NODE_BINARY_PACKAGE_PREFIX=@my-node-releases/"

@adabru
Copy link

adabru commented Apr 9, 2021

Here they are: https://unofficial-builds.nodejs.org . Unofficially "un"maintained by a member of the nodejs build working group. Here is a comment referring to it as solution to an issue: nodejs/build#1140 (comment) . They are not made officially because that would consume more server capacity for testing and more issues in the official issue tracker than the nodejs team is organized to handle. That's at least what I understood from the various discussions in their issue tracker.

Alternatively one can use the nodejs docker images, see https://hub.docker.com/_/node.

Or a 'use this flavor of unofficial binaries' -- like "NODE_BINARY_PACKAGE_PREFIX=@my-node-releases/"

Seems good to me.

EDIT: There are only the 64-bit binaries (linux-x64-musl), not the 32-bit ones.

@aredridel
Copy link
Owner

Ooh excellent. I'll see what it might take!

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

No branches or pull requests

3 participants