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

Update Node to v6 (or 8 ???) on aarch64 #29

Closed
vielmetti opened this issue Apr 3, 2017 · 3 comments
Closed

Update Node to v6 (or 8 ???) on aarch64 #29

vielmetti opened this issue Apr 3, 2017 · 3 comments

Comments

@vielmetti
Copy link
Contributor

On aarch64, the version provided still pulls in Node 4, instead of Node 6 like all the rest.

It should be a simple one-line fix to the FROM line in the Dockerfile, but there's a small snag in Node version naming at Docker hub. I don't want to pull in some specific point release of Node, just whatever is latest for 6.

See tianon/jenkins-groovy#21 for the naming issue on Docker hub, and when it gets resolved this will be very easy to resolve as well.

@dceejay
Copy link
Member

dceejay commented Feb 15, 2018

Should this now also be node 8 ? and move to the newer official repo ? https://hub.docker.com/r/arm64v8/node/

https://github.com/docker-library/official-images#architectures-other-than-amd64

@dceejay dceejay changed the title Update Node to v6 on aarch64 Update Node to v6 (or 8 ???) on aarch64 Feb 15, 2018
@vielmetti
Copy link
Contributor Author

It'd be really nice to package this as a multiarch repo, perhaps even in the official repos. I'll ping @tianon to see what he thinks.

@dceejay
Copy link
Member

dceejay commented Sep 30, 2019

Node-RED 1.0.0 is now available on docker hub - https://hub.docker.com/r/nodered/node-red.

This closes this issue.

There are a few changes to the new release, please read the README for further details.

@dceejay dceejay closed this as completed Sep 30, 2019
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

Successfully merging a pull request may close this issue.

2 participants