You can set shell command by SHELL and simply call RUN rvm install 2.3.3.Īfter this your Dockerfile gets a lot cleaner. It was only after building a rvm container that I came across this Stack Overflow Answerĭon’t use RUN bash -l -c rvm install 2.3.3. nvmrc file in your folder as a single point where you document the used node version. If you’re using nvm instead of a Docker hub image it’s better to use the. The reason why I’m writing this post is because most of the answers out there are giving advise that feels just wrong. Which is quite logical because its a developer tool and you wouldn’t want switching environments to have system-wide effects. This is because nvm uses environment variables that are declared in the profile. nvmrc file for determining which node version to use.īuilding this container appeared to be harder than I expected. And perhaps it’s actually more maintainable if the Dockerfile uses the. Usually I would opt for using a Docker image FROM node: but the version in use (perhaps for good reason) isn’t on Docker hub. Being more of a backend / devops developer myself I hadn’t really used nvm before.

I was building containers for a client where the codebase for historical reasons uses a few different node versions. It can be a useful thing to know nonetheless.

Mainly because you shouldn’t use it without knowing the implications. If thenĮlif thenįi elif & then echo 'Reverting to nvm default version'įor more details visit nvm shell integration.Recently I came across a solution to a Docker specific problem that I didn’t know about and that I think is not used very often. To automatically call nvm use put the following at the end of $HOME/.bashrc: cdnvm() ')')

Change nvm version