Officially support Alpine linux

[xzyfer]

What

We do not currently support Alpine Linux. It is commonly used to as a minimal base image with docker. Given the rising popularity of docker (and containerisation in general) I believe supporting Alpine Linux with a pre-built binaries is the right thing to do for the community.

Why

There is not explicit reason for us not supporting Alpine Linux, nor did make a conscious decision not to. We prebuild a "Linux" binaries which is targeted at popular distributions, namely those derived from Debian with a special consideration for CentOS 5. However that Linux is not compatible with the versions of libc(?) that ship with Alpine.

How

To achieve this we need to two things from the community.

Firstly we need a Dockerfile that when run for a given node-sass commit-ish, compiles the node-sass binary for all 32bit and 64bit version of Node 0.10, 0.12. iojs 1, iojs 2, iojs 3, Node 4, Node 5, Node 6. For reference here is the one we use for the Linux binaries

Secondly a JavaScript function that reliable detects the current OS is Alpine Linux.

[amrocha]

Hey, I'm looking into getting this done. I'm working off a version of the Dockerfile you linked. Still not sure how to detect Alpine as the current OS but I haven't thought too much about it yet.

[xzyfer]

@amrocha currently we detect the underlying OS using process.platform. This however return linux Alpine. What we need is a way to differentiate Alpine from other linux distributions. This way we can download an alpine specific binary when installing rather than the generic linux binary.

There's some background information #756 where something similar was previously discussed to distinguish between different FreeBSD binaries.

[saper]

Can somebody drop the contents of the process node variable when running node on alpine? I don't think nodejs.org provides the Alpine-based build: what kind of build are people using to run node on that platform?

[xzyfer]

@saper I've asked for help from the Twitterspehere

[amrocha]

So here's where I am:

• NVM doesn't support Alpine because it downloads pre-compiled node binaries, and Node doesn't provide Alpine binaries either;
• Alpine's package manager doesn't have IO.js or older versions of Node available as a package, and doesn't let you choose if you want the 32 bit or 64 bit version of a package so that doesn't work either;

What I'm doing right now is downloading the Node source and building it for every single version node-sass supports, but I'm having internet speed issues at home right now so I can only really get any progress done on this when I'm at work.

[xzyfer]

Thanks for looking at this. If you make the dockerfile a gist that'd be
great. If alpine doesn't official support iojs then we possibly don't need
to bother with those binaries.
On 19 Jun 2016 2:47 AM, "Andre" notifications@github.com wrote:

So here's where I am:

• NVM doesn't support Alpine because it downloads pre-compiled node
  binaries, and Node doesn't provide Alpine binaries either;
• Alpine's package manager doesn't have IO.js or older versions of
  Node available as a package, and doesn't let you choose if you want the 32
  bit or 64 bit version of a package so that doesn't work either;

What I'm doing right now is downloading the Node source and building it
for every single version node-sass supports, but I'm having internet speed
issues at home right now so I can only really get any progress done on this
when I'm at work.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1589 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAjZWOH9N-npSNazTnn9sUyAlJCiNaKBks5qNCE3gaJpZM4IzxUh
.

[amrocha]

Here's the dockerfile I'm using:
https://gist.github.com/amrocha/56ffd0246a8bf31b72ae4667fbd1ea99

Alpine's package manager, apm, provides the following node versions:

• 0.10
• 0.12
• 4.x
• 5.x
• 6.x

I'll try asking the maintainer for the node package if there's a way of specifying if you want the 32 or 64 bit version, but it doesn't seem like there is.

[xzyfer]

@amrocha thank you for your work on this. If 32bit version are difficult to by I wouldn't bother until someone requests it.

[xzyfer]

I would simply stick to the versions of Node made available via apm.

[amrocha]

@xzyfer that should be a lot easier, I'll see if I can get something together by the end of the day today

[amrocha]

So I dug in a little bit more and turns out I was wrong about the versions of node Alpine provides. The versions above are all the versions that it has provided at some point in time, but you can only download the latest version.

Sorry about the confusion, I didn't expected that older versions would be unavailable.

[saper]

@amrocha maybe there is a way to retrieve old package building information and re-build the node binaries yourself? For FreeBSD I have recovered old definitions and I keep using them to have older io.js binaries available.

[amrocha]

@saper I could look into doing something similar, is there any difference between doing that and just building node from source though?

[xzyfer]

Building from source is fine :)
On 22 Jun 2016 10:47 AM, "Andre" notifications@github.com wrote:

@saper https://github.com/saper I could look into doing something
similar, is there any difference between doing that and just building node
from source though?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1589 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAjZWKl3rzV1YowXitOQf2P8qc3MkOpEks5qOIYQgaJpZM4IzxUh
.

[spralle]

Any progress on this? I think it would help a lot of people!

[amrocha]

Sorry I haven't had much time to work on this. I want to build all the node versions first, and then compile the node-sass binaries for each of them, that way the node versions will be cached and you won't have to build them every time a new version is released. The Dockerfile I linked above works, but since there's no node version managers that work in Alpine I don't have an easy way to switch between versions. I was going to write my own simplistic implementation but just haven't had time to do it.

[spralle]

I'm not sure if I understand what you want to do, but can't you just use the same way like this image is doing to get different node versions?

https://github.com/mhart/alpine-node/blob/master/Dockerfile

[amrocha]

That is pretty much what I'm doing, but I need to have multiple versions of node installed at the same time so I also need a way of managing versions.

[jgallen23]

It might be easier to not try to build multiple versions of node at the same time. Just create a Dockerfile that has the node-sass stuff in it and then starts with FROM mhart/alpine-node:X.X.X. Then just change the version, build, and repeat for all the version numbers you want to support. I think on recent versions of docker, you can pass in environment variables to the build command so it could be as simple as something like NODE_VERSION=4.4.7 docker built -t node-sass:4.4.7 .

[spralle]

I agree, I think that would be the easier way forward...

[amrocha]

Got some time to work on this again and wrote up a script that does what @jgallen23 suggested:

https://gist.github.com/amrocha/d7328f2d637745597fb5f46aad32f327

@xzyfer does this work for you?

[superlbr]

seems little problem in merge?

[superlbr]

going to bump a new version?@xzyfer

[xzyfer]

This should be fixed in v4.1.0. Please test it out and let us know. A big thank you to @lox and @S-YOU.

[FernandoMiguel]

coming at this now.
is there anything i need on my alpine docker for this to work?
any env var?

[xzyfer]

Check the node-sass release notes for the Alpine compatibility table

…

On Wed., 27 Jun. 2018, 9:01 pm Fernando Miguel, ***@***.***> wrote: coming at this now. is there anything i need on my alpine docker for this to work? any env var? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#1589 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWBAKTEES7ZbeTS6mecImb803NTZrks5uA2YWgaJpZM4IzxUh> .

[ralyodio]

Check the node-sass release notes for the Alpine compatibility table

How do I do that? Got a link?

[saper]

How do I do that? Got a link?

For example for this release

https://github.com/sass/node-sass/releases/tag/v4.13.0

there is a table that says

Supported Environments

OS	Architecture	Node
Windows	x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
OSX	x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13
Linux*	x86 & x64	0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**^, 12**^, 13**^
Alpine Linux	x64	6, 8, 10, 11, 12, 13
FreeBSD	i386 amd64	6, 8, 10, 12, 13

[ralyodio]

When I use `node:10-alpine` it says there are no node-sass bindings for my platform.

…

On Thu, Jan 2, 2020 at 2:46 PM Marcin Cieślak ***@***.***> wrote: How do I do that? Got a link? For example for this release https://github.com/sass/node-sass/releases/tag/v4.13.0 there is a table that says Supported Environments OS Architecture Node Windows x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13 OSX x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13 Linux* x86 & x64 0.10, 0.12, 1, 2, 3, 4, 5, 6, 7, 8**, 9**, 10**^, 11**^, 12**^, 13**^ Alpine Linux x64 6, 8, 10, 11, 12, 13 FreeBSD i386 amd64 6, 8, 10, 12, 13 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1589?email_source=notifications&email_token=AAAGV5OWSRWOXF6UCJVZ75TQ3ZVGBA5CNFSM4CGPCUQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH7WCAI#issuecomment-570384641>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAGV5OQDWKM4E4BYCXXSPTQ3ZVGBANCNFSM4CGPCUQQ> .

-- Anthony Ettinger http://anthony.ettinger.name anthony@ettinger.name +1 (831) 406-1123

[saper]

When I use node:10-alpine it says there are no node-sass bindings for my platform.

please provide all the information in #2812