nodejs-docker | 当Node.js遇见Docker - 当Node | Continuous Deployment library

I figured it out, it was just a simple path arror in the middleware (picUpload.js)

cb(null, '/src/public/media/pictures');

I believe you should not be using directory paths the way you're doing, just use the directory name directly. --watch src bin instead of --watch . ./bin. I think nodemon internally uses glob or something to resolve that path and if you use ./ it will break it (I'm not sure about that).

Also don't watch all possible files on root, specify the directories you actually want to watch, otherwise you're adding a lot of additional recursive watching on unnecessary things.

https://github.com/remy/nodemon#monitoring-multiple-directories.

Reading further down their documentation, they also mention that in some cases using containers with a mounted drive can cause issues and they then recommend using the --legacy-watch flag, which will internally then use chokidar. That's something you can try if fixing the path name doesn't work.

I believe your issue is [nodemon] watching path(s): *.*, the ./ is resolving incorrectly and tries to watch on all paths or something.

Something else to note is that nodemon will run in the current working directory, so if you are using --watch src bin make sure you're actually in the project root when you run that.

Try out by editing your docker compose, you have a problem in your volumes that is copying the hole project directory.

replace

This is because of multi layer builds within Docker. Every layer(/step) is cached, so this way the NPM install will not be run every time you change the source code, but only when the package.json or package-lock.json is changed.

I think you are missing the following important part, should be placed after you have RUN npm install:

To bundle your app's source code inside the docker image, use the COPY instruction:

It actually does not really matter where the CMD is located. It'll remain the command execute by docker when the container is generated.

Since the content of the folder does not affect the steps inside the image, it makes sense to have it as last available step to use the cache at its best (even though it does not really affect much there).

I used to get this error due to low or intermittent internet bandwidth.

Change docker exec mynodeapp -it /bin/bash to docker exec -it mynodeapp /bin/sh

According to docker documentation the correct syntax is the following:

docker exec [OPTIONS] CONTAINER COMMAND [ARG...]

• -i and -t are the options
• mynodeapp is CONTAINER
• /bin/bash - is a COMMAND inside container

And another problem is that there is no bash shell inside container, so you can use sh shell.

It can be anything. Tutorial just used a random port. You can change it whatever you want. Then you can access your node-web-app running inside container at port 5001 at localhost:49160 from your host machine.