Correctly Configure Docker Node Pinning

[FireLemons]

Relying on the ruby alpine image for node does not allow us to specify which major version we use. It was the solution for a while because the version of node we wanted just happened to be the same as the node from that image.

Currently we are using an old solution that does allow for custom node version in our image. However the repo we are getting node from is the latest alpine image which has a version of node that updates somewhat frequently which makes the method of pinning in this solution cause a conflict as soon as it updates.

[FireLemons]

@stefannibrasil we had an incorrect docker config. Just wanted to ping you in case you picked up some bad info from working on it earlier

[stefannibrasil]

oh, interesting, thanks for the heads up. What error were you getting?

[stefannibrasil]

@FireLemons I see new PRs are broken now, sorry about that! Do you want to maybe revert #6708 and I can take a look? Weird that CI was green when that one was merged.

[FireLemons]

@stefannibrasil I meant that pinning node that way in our Dockerfile is suboptimal and you shouldn't do it in other places like that

[FireLemons]

Turns out the solution was just to copy the binaries from the node image. I spent a long time tying to copy just the built assets from a build step before remembering the docker image requires node and npm because it's a development environment too.