Laurent Goderre

I'm not sure we are ready to take on another of these breaking changes

@peperoni60 the images now have a non root user and group that can be used for running `npm install` this should solve your issues.

Couldn't you create a group called `node` and add your user to it?

@tianon any idea?

If I remember correctly, folder created by `WORKDIR` are owned by root even if they are created after the `USER` directive. Try creating the folder first

@frankchen76 you need to bind a host port to the container port at runtime. Are you doing `docker run` or are you using `docker-compose`?

What is the output of `docker ps`?

So it is bound properly. Are you sure a process is listening on those ports in the container?

My first guess for a culprit would be using `npm install` using the `root` user instead of `node` user. If you add `-u node` to your command, do you get...

I agree but we use the official distribution which include npm. The core node doesn't have a version of node without npm, as far as I am aware.