INFO RUN apt-get update >/dev/null & apt-get install -y curl >/dev/null & apt-get -y autoclean >/dev/nullĭebconf: delaying package configuration, since apt-utils is not installed
INFO RUN rm /bin/sh & ln -s /bin/bash /bin/sh INFO Unpacking rootfs as cmd RUN rm /bin/sh & ln -s /bin/bash /bin/sh requires it. INFO Retrieving image node:slim from registry # this file contains deeper shell integration ->ĮNV NODE_PATH $NVM_DIR/v$NODE_VERSION/lib/node_modulesĮNV PATH $NVM_DIR/v$NODE_VERSION/bin:$PATHīuilding docker image log Building Docker image for: nvm-docker-image nvmrc file contains string "16.14.1" which is the node_version i need to runĬOPY. Could someone have any idea about this issue? please find the docker file and image building log below. nvmrc file to automatically install and use the node version, but after building my dockerfile, it is using always the Default version as default -> 18.3.0 (-> v18.3.0 *) even though using this version "v16.14.1". RUN source $NVM_DIR/nvm.sh \ & nvm -version works as well. Just curious, is that sub-shell behavior documented in their docs? 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 & ln -s /bin/bash /bin/shĮNV NODE_PATH $NVM_INSTALL_PATH/lib/node_modules
# Installation of NVM, NPM and packages RUN mkdir /usr/local/nvmĮNV NVM_INSTALL_PATH $NVM_DIR/versions/node/v$NODE_VERSION Make sure $NVM_DIR is not pointing to something like ~/.nvm because the link will be wrong, pointing to root's user home directory. RUN ln -sf NVM_DIR/versions/node/v$NODE_VERSION/bin/npm /usr/bin/npm RUN ln -sf NVM_DIR/versions/node/v$NODE_VERSION/bin/node /usr/bin/node RUN ln -sf NVM_DIR/versions/node/v$NODE_VERSION/bin/node /usr/bin/nodejs Otherwise, without synlinks > docker run nvm node -vĭocker: Error response from daemon: OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"node\": executable file not found in $PATH": unknown.ĮRRO error waiting for container: context canceledīut if you TTY into container docker run -i -t nvm it would work regardless.Īlso, if someone builds Docker Image using custom user, you got to create symlinks with a root account, therefore: USER root Thanks, Symlinks are required if a command is passed after docker run, like: > docker run nvm node -v
0 kommentar(er)
