-
Notifications
You must be signed in to change notification settings - Fork 2k
Added multiple versions of alpine linux #725
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
Conversation
5062729 to
505ffde
Compare
906baba to
b773635
Compare
b773635 to
76be1c7
Compare
|
I'm excited :D |
|
I'm a bit worried about the build time, and how it would affect our ability to get security releases out in time |
|
Yeah hopefully we can get the alpine cache merged before this one. |
|
That won't help the build for docker hub. They might build in parallel though, so no big impact |
|
It would be nice if anyone could access the Travis cache so that even the hub could use it. |
|
Ref nodejs/security-wg#168 (comment)
I think the real solution for our speed woes is to get a prebuilt binary. |
|
Yeah, I agree. Is there anyone on the build group who can help push that forward? |
|
From what I have read, they aren't too keen on this because of the static typing which would mean they would need to track Alpine security updates. |
|
I think this is the most current issue: nodejs/build#1140 |
3030a2e to
24f06a6
Compare
|
Stackbrew generates: |
24f06a6 to
e514c19
Compare
e514c19 to
8042599
Compare
8042599 to
8366e9b
Compare
|
Following up on @LaurentGoderre's last comment:
To me this means Alpine isn't something they are willing to support. If it's not a supported platform, maybe we shouldn't be encouraging people to use it by offering multiple versions? I don't know, I'm beginning to think this is not the best use of our time and maybe we just need to revisit upgrading the Alpine images to the latest supported version (3.7) |
|
This allows us to upgrade alpine versions in a less disruptive way. For example, when 3.8 comes out, we could support v3.6 for two versions, keep the default on 3.7 for two versions and then drop 3.6 and move the default to 3.8. |
|
Yes it would be less disruptive, but I just don't think it's that important. Based on the issues and PRs people have submitted, they seem to care more about Alpine being out of date than being able to pin to given Alpine release. I think we should just treat Alpine updates the same way we do Yarn updates and move on. I think a stronger argument can be made taking this approach with Debian and possibly ubuntu (especially given how small Bionic is now) and we wouldn't have to worry about absurd build times. |
|
Alright! |
|
@chorrell does that mean that next version of Node 6 should move to Alpine 3.7? |
|
Yep |
|
Maybe we can salvage part of this too make it easier? |
|
Yeah, that would be good. |
Implements #473
TODO:
alpinetag