Update to node 8.1.0

[SimenB]

https://nodejs.org/en/blog/release/v8.1.0/

[SimenB]

I don't have merge-permission here, so someone else has to merge. IDK what the policy are for number of approvals either

[cebor]

When will this pushed to docker hub?

[SimenB]

I have never done that before. Is it just running generate-stackbrew-library.sh and PRing the result?

[pesho]

@SimenB yes. You run generate-stackbrew-library.sh on master after merging, and PR the result to https://github.com/docker-library/official-images/. Usually whoever merges the PR also does the Docker Hub submission but in this case @LaurentGoderre forgot.

[LaurentGoderre]

I didn't forget....I didn't know about that part, sorry.

[hnryjms]

If anyone's interested, we could probably configure Travis CI to automatically deploy images and make the PR based on the master branch. I've never contributed here, but I'd take a stab at it.

[SimenB]

The images aren't deployed from this repo. See e.g. docker-library/official-images#3039

[SimenB]

Let's try it 🙂
docker-library/official-images#3046

[SimenB]

This is now available on docker hub

[westy92]

Is there any reason why these newly-pushed images aren't getting scanned for vulnerabilities like the rest?

[SimenB]

Hmm, I have no idea 😕

[yosifkit]

The system Docker uses on the Hub can take a little while to get though the scanning.

[westy92]

The scanning can take a while (sometime up to a few hours), but in these cases there is an indicator that it is currently being scanned. That is not the case with these.

[tianon]

cc @toli (scanning seems to be delayed or stuck on the new node:8.1 tags? normal queue behavior, or something else going on?)

[westy92]

The 6.11.0 tags are stuck as well.

8.0.0 was stuck before but I contacted Docker support and they manually kicked off those scans.

[toli]

This may be a bug on my end, i'm seeing the pushes come in but not forwarding on to scanning.
i've manually submitted all {{node}} tags for rescan again, will be investigating the bug.