Laurent Goderre

How about ``` docker run --rm -it -v $PWD:/opt/ct -w /opt/ct node:8.15.1 sh -c "env foo:bar:baz=jazz && yarn env | grep foo" ```

This doesn't seem to be an issue with the image but with the install scripts for one of the dependencies failing. Perhaps one of your dependencies relies on node binding...

It seems like an issue with running npm. Are you sure the command is running from the dir your expect it to? If you run `npm start` but there is...

If you can play a bit with your k8s deployment, I would try overriding the container definition to use a custom command for the container and do a `pwd` or...

I am hesitant to introduce a tag that isn't standard in either docker or nodejs. We tag based on what the core node project uses.

@rvagg is this something the core Node project ever consider using?

It's not hard to add but I don't want add semantic problems. For example `old` could be confused as EOL so the name of the tag is somewhat important.

I think this is due to run npm as root. You should run it as the `node` user

Yeah, it is definitely awkward. @SimenB does this folder even exist before running npm to begin with?

Ooooh it does!!!