![]() That clears up the confusion I was having on why I kept nvm not found. This worked for me! Thanks for the explanation about how Docker RUN opens its own "sub-shell" on each RUN command. ![]() I believe it has to do with docker RUN opening its own "sub-shell" and it does not automatically load your contents of. Of course, this is dependant on where your. I'm running nvm 0.37.2 and I noticed that if you source your ~/.bashrc right before calling nvm, it'll work. I had the same issue with trying to run RUN nvm -v in the dockerfile as well. RUN rm /bin/sh
0 Comments
Leave a Reply. |