NPM is 2.14 not 3.5.2 (using node:4.2-wheezy image)

[SamMorrowDrums]

NPM install fails for me, and it is reporting that the version is: 2.14.12, I believe this fixed in later versions of NPM but I am confused as to why I'm even using npm 2.

Step 0 : FROM node:4.2-wheezy
 ---> 005063d24086
Step 1 : RUN npm install --global gulp
 ---> Running in 68159de6a2fc
npm info it worked if it ends with ok
npm info using npm@2.14.12
npm info using node@v4.2.4
npm info addNameTag [ 'gulp', 'latest' ]
npm info attempt registry request try #1 at 12:18:56 PM
npm http request GET https://registry.npmjs.org/gulp
npm info retry will retry, error on last attempt: Error: self signed certificate

[SamMorrowDrums]

OK, I tried with 5 image, and still getting issue, so perhaps I have an issue with my server config.

Status: Downloaded newer image for node:5-wheezy
 ---> 9eadfadbb80c
Step 1 : RUN npm install --global gulp
 ---> Running in af685962f860
npm info it worked if it ends with ok
npm info using npm@3.3.12
npm info using node@v5.3.0
npm info attempt registry request try #1 at 12:23:58 PM
npm http request GET https://registry.npmjs.org/gulp
npm info retry will retry, error on last attempt: Error: self signed certificate

[Starefossen]

Node.js v4.2.4 'Argon' (LTS) ships with npm 2.14.12.

From the Node.js v4.2.4 Changelog:

• deps: Upgrade to npm 2.14.12 (Kat Marchán) deps: upgrade to npm 2.14.12 node#4110

This is the true for the Official Node.js :4 and argon Docker Images:

$ docker run --rm -it node:4 npm --version
> 2.14.12

[SamMorrowDrums]

No problem, I'm just assumed wrongly it was old NPM. I'm looking into what is breaking certificate chain now!