You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2023. It is now read-only.
** PLEASE ONLY USE THIS ISSUE TRACKER TO SUBMIT ISSUES WITH THE DOCKER LABS TUTORIAL CONTENT **
If you have a bug working with Docker itself, not related to these labs, please file the bug on the Docker repo *
If you would like general support figuring out how to do something with Docker, please use the Docker Slack channel. If you're not on that channel, sign up for the Docker Community and you'll get an invite. *
** PLEASE ONLY USE THIS ISSUE TRACKER TO SUBMIT ISSUES WITH THE DOCKER LABS TUTORIAL CONTENT **
Please provide the following information so we can assess the issue you're having
Which lab is it that you're having issues with?
https://github.com/docker/labs/tree/master/developer-tools/nodejs-debugging
Description
During the "Fix the bug" step, the nodemon tool doesn't catch file changes and restart the the app.
According to this post, and the nodemon documentation, when running nodemon inside a container, you have to use Legacy watch (-L).
This should be reflected in the docker-compose.yml file.
Steps to reproduce the issue, if relevant:
Describe the results you received:
No file change, app restart.
Describe the results you expected:
nodemon should register the file change, and restart the app.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, Docker for Mac, Docker for Windows, VirtualBox, physical, etc.):
Docker for Windows
Windows 10 Pro
The text was updated successfully, but these errors were encountered: