Add tags for every new version of node

[manast]

In order to use this image in production we need version tags.

[vvo]

yes we should always have tagged version for any dockerflie

[manast]

Could you please add tags? it should pretty straightforward, just tag the image everytime nodejs is updated... otherwise this image is quite difficult to use in production. We could have an alternative proper nodejs image, but since this is the official trusted one, it is really a shame that we can't use it just because you don't tag the images when building them.

[manast]

please add image tags! make this image useful!

[manast]

Well in case you want a proper tagged and also based on phusion-baseimage, you can get one here:
https://registry.hub.docker.com/u/optimalbits/nodejs/

[jareware]

Agreed, you can't just depend on latest and hope stuff works. Tags would be hugely appreciated.

[adam-beck]

Why is this not being addressed? Seems like a trivial change.

[jareware]

@adam-beck: node.js (along with a whole bunch of other important bases) are actually covered in the Docker Hub by official images, e.g. https://registry.hub.docker.com/_/node/, which are carefully maintained, tagged etc.

The "dockerfile" project, while often high up on the the Google results, contains mostly abandonware by comparison.

[manast]

the official image is based on Debian, which may or may not be what you need...

[manast]

Btw, this image was updated a month ago, so not being tagged may not be as much being abandonware as being lame :)

[jareware]

@manast: not picking on this repo in particular, just my general observation of things under github.com/dockerfile, feel free to disagree. :)

[nomadster]

@manast how exactly tagging works?

[manast]

@nomadster you need to read docker images documentation, its quite basic stuff: https://docs.docker.com/userguide/dockerimages/

[nomadster]

Oh seems pretty simple and legit. Let's see if I can find some time later to add this on the PR I've made (#7).

👍