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:

  • Restart flask app in docker on changes
  • Setup local WordPress development environment with Docker error 500
  • starting container using docker API
  • What are the differences between sharing a dockerfile on git and sharing a docker container?
  • chown in docker not changing user to root
  • “docker run swarm create” failed with error “503 Service Unavailable”
  • 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.

  • communication between containers in docker
  • Copy from docker to host inside CI build
  • Deploying Docker Swarm mode services across multiple failure domains
  • Docker-Squash command not working
  • Docker: Expose a range of ports
  • When docker run, an error occurs. “ValueError: Unable to configure handler 'watchtower': You must specify a region.”
  • 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.