Docker nodejs not found

When i run docker build -t example . on the below im getting an error

FROM ruby:2.1
RUN rm /bin/sh && ln -s /bin/bash /bin/sh
ENV NVM_DIR /usr/local/nvm

RUN curl | bash \
  && source $NVM_DIR/ \
  && nvm install $NODE_VERSION \
  && nvm alias default $NODE_VERSION \
  && nvm use default


RUN node -v

I get the following error:

  • docker error Unable to locate package cowsay
  • Docker ONBUILD COPY doesn't seem to copy files
  • Docker Compose: initialize / customize images from hub on the fly & run
  • Git clone via HTTPS not working in Docker makefile
  • docker volume - who overrides who - file within docker or existing file outside?
  • Zero Downtime app deployment with CoreOS
  • Step 9 : RUN node -v —> Running in 6e3fac36d2fc /bin/sh: node:
    command not found The command ‘/bin/sh -c node -v’ returned a non-zero
    code: 127

    Can’t understand why node is not found in the path. i tried executing the file as well but it didnt have an effect.

  • How to scale application with multiple exposed ports and multiple volume mounted by using docker swarm?
  • ASP.NET Core 1.0 RC1 Docker with dnu publish
  • Install pylint in Alpine Linux based Docker Image
  • Docker continuous deployment workflow
  • How does Docker for Windows run Linux containers?
  • Looking for a Docker image that automatically detects the application language
  • One Solution collect form web for “Docker nodejs not found”

    Node version manager is an excellent application for switching versions of Node.js on your development machine, but Docker begs a specific kind of image/container design that is meant to be both ephemeral and stripped down to the bare essentials in order to support the “best practice” of microservices. Docker is just a fancy way to run a process, not a full VM. That last sentence has helped me a lot in how to think about Docker. And so here, you can make things easier on yourself by creating different versions of your image, instead of making one container with many versions of Node.js inside of it. This way, you can reference the Node version you want to run inside of your docker run command instead of trying to feed in environment variables trying to get NVM to select the right version. For example:

    docker build -t=jamescharlesworth-node:4.x-latest .

    And of course your Dockerfile will have in it the install command in your RUN directive that you mention in the comments:

    RUN curl -sL | bash - 
    RUN apt-get install -y nodejs
    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.