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 # add node and npm to path so the commands are availableĮNV NODE_PATH $NVM_DIR/v$NODE_VERSION/lib/node_modulesĮNV PATH $NVM_DIR/versions/node/v$NODE_VERSION/bin:$PATH # install node and npm, set default alias & apt install -y -q -no-install-recommends \ RUN rm /bin/sh & ln -s /bin/bash /bin/shĮNV ACQUIRE_DEPENDENCIES "apt-transport-https ca-certificates curl gnupg git openssh-client" # Replace shell with bash so we can source files Additionally, is it implied that we've written a separate $NVM_DIR/nvm.sh? FROM ubuntu:18.04 Check your profile files and environment. This Dockerfile template blows up on me when it gets to setting the NVM_DIR env var: You have $NVM_DIR set to "/usr/local/nvm", but that directory does not exist.
0 kommentar(er)
