Fix dockerfile -> Adding manually missing Python dependency prior to npm install and npmrc

[danielherrerohernando]

Using node-alpine, when building a docker image, we are getting an error related to some Python missing dependency, this PR fixes that.

Log with the aforementioned error when building image:
https://drive.google.com/file/d/11kyHQ2nxtnEp-pYW1nQB0SafE9K8bGWT/view?usp=sharing

Further info -> nodejs/docker-node#282

Also this PR adds the .npmrc file (@kevinccbsg )

[kevinccbsg]

The .npmrc file looks good to me!!

[danielherrerohernando]

@MatteoDiPaolo @feliun @w3dani

[MatteoDiPaolo]

@w3dani please have a look at it, I'm not sure if there is another way of doing it.

[feliun]

I don't think this has bad implications, but I'm interested to know about the root cause for this error, I'd be surprised if the node alpine image wasn't prepared to build because of a missing dep? @w3dani thoughts?

[danielherrerohernando]

@feliun The reason for the error seems to be simple, node-alpine versions do not have Python installed, so when building the image, npm install command throws an error because some dependency needs Python.

Using the --virtual flag in the RUN command (part of Alpine´s APK) we can run npm install with Python installed and, after npm install finishes, Python is uninstalled.

Apart from the original link on the first comment, here you can find other issues where people realize about missing Python on Alpine:
nodejs/docker-node#384
nodejs/docker-node#715

[w3dani]

The main goals of using alpine images are:

• Increase the speed of the CICD pipeline
• Generate lighter artifacts

This change would impact on the first point so it would be interesting measure the impact. Apart from this, I don't see any problem.
There is another point of view. The problem is we need to install python because bcrypt uses node-gyp and this one needs python. Other solutions could be:

• Use another package different from bcrypt, which does not use node-gyp.
• Check the need of add this change to the yeoman template (we are not using bcrypt or any other package using node-gyp in shop, so it could not be really a need for all the projects). Maybe this must be only in those projects which are using those packages (however, sooner or later some other package we need could also use node-gyp)

[w3dani]

It's ok for me if we agree in looking over the dependencies used in the future

[kevinccbsg]

@danielherrerohernando @w3dani @MatteoDiPaolo @Betisman could we merge this and before merge this update the Dockerfile version to at least 12?

[Betisman]

In order to approve the PR, I would like to know about the points @w3dani explains in #6 (comment). They seem to be interesting.

Ok, I see @w3dani already approved it, so I guess we're ready to merge this.

[Betisman]

Well, @kevinccbsg after a second reading of your comment, you're proposing to update the Dockerfile in this same PR and then merge it, right?

[MatteoDiPaolo]

Go ahead guys!!!

[danielherrerohernando]

11 months later this PR will be merged, #emotion 😢

[MatteoDiPaolo]

11 months later this PR will be merged, #emotion 😢

It took more than deliveringg a baby

[kevinccbsg]

Well, @kevinccbsg after a second reading of your comment, you're proposing to update the Dockerfile in this same PR and then merge it, right?

Yes, that's my plan and also update dependencies.

[kevinccbsg]

I cannot modify this branch as it is a PR from another fork so I'm going to merge it