Docker-compose: node_modules not present in a volume after npm install succeeds

by

This happens because you have added your worker directory as a volume to your docker-compose.yml, as the volume is not mounted during the build.

When docker builds the image, the node_modules directory is created within the worker directory, and all the dependencies are installed there. Then on runtime the worker directory from outside docker is mounted into the docker instance (which does not have the installed node_modules), hiding the node_modules you just installed. You can verify this by removing the mounted volume from your docker-compose.yml.

A workaround is to use a data volume to store all the node_modules, as data volumes copy in the data from the built docker image before the worker directory is mounted. This can be done in the docker-compose.yml like this:

redis:
    image: redis
worker:
    build: ./worker
    command: npm start
    ports:
        - "9730:9730"
    volumes:
        - ./worker/:/worker/
        - /worker/node_modules
    links:
        - redis

I’m not entirely certain whether this imposes any issues for the portability of the image, but as it seems you are primarily using docker to provide a runtime environment, this should not be an issue.

If you want to read more about volumes, there is a nice user guide available here: https://docs.docker.com/userguide/dockervolumes/

EDIT: Docker has since changed it’s syntax to require a leading ./ for mounting in files relative to the docker-compose.yml file.

More Related Contents:

  1. MongoDB on with Docker “failed to connect to server [localhost:27017] on first connect “
  2. Docker Error bind: address already in use
  3. ECONNREFUSED for Postgres on nodeJS with dockers
  4. Docker – SequelizeConnectionRefusedError: connect ECONNREFUSED 127.0.0.1:3306
  5. How to set npm credentials using `npm login` without reading from stdin?
  6. Use docker run command to pass arguments to CMD in Dockerfile
  7. Error: Redis connection to 127.0.0.1:6379 failed – connect ECONNREFUSED 127.0.0.1:6379
  8. Why does `package-lock.json` causes a failure in a docker container build when `npm install`?
  9. Why COPY package*.json ./ precedes COPY . .?
  10. Node.js connect to MySQL Docker container ECONNREFUSED
  11. How to install nvm in docker?
  12. How to cache the RUN npm install instruction when docker build a Dockerfile
  13. replacing a placeholder in a html file with 1-n specific values defined in a config.json using shellscript [closed]
  14. Communication between multiple docker-compose projects
  15. Cloud Functions for Firebase – Billing account not configured
  16. Cannot install packages using node package manager in Ubuntu
  17. How can I set the default timezone in node.js?
  18. Error: unable to verify the first certificate in nodejs
  19. How do I determine the current operating system with Node.js
  20. Node.js – EJS – including a partial
  21. Change default global installation directory for node.js modules in Windows?
  22. Communications link failure , Spring Boot + MySql +Docker + Hibernate
  23. How can I use environment variables in docker-compose?
  24. More than 10 lines in a node.js stack error?
  25. How to wait for a stream to finish piping? (Nodejs)
  26. How/why does npm recommend not running as root?
  27. bower command not found
  28. Obtaining the hash of a file using the stream capabilities of crypto module (ie: without hash.update and hash.digest)
  29. Displaying an image with EJS in node.js/express
  30. How to chain a variable number of promises in Q, in order?

Leave a Comment