Why Isn’t Hot Reloading Working with Docker?

It sounds like you're trying to set up a development environment with hot reloading using Docker, right? Essentially, for hot reloading to work, you need to ensure that your source code changes in your host machine are reflected inside the container. You’re on the right track with using volumes to bind your local src directory to the /app/src directory in the container.

However, a common issue is how you're running your app inside the container. Make sure that the command in your Dockerfile (like `yarn dev`) supports hot reloading. Double-check your setup and scripts to ensure everything's configured correctly for that.

Hot reloading is a feature that works in a development setup and allows your app to update in real-time as you make changes. Ensure that you're using a Node.js framework that supports hot reloading, like Next.js or similar. If your Dockerfile mentions `yarn dev`, just ensure that the tool you're using respects the environment variable changes and can properly watch those file changes.

Also, Docker does indeed tend to run more effectively with two separate configurations: one for development where hot reloading is needed, and one for production that optimizes performance.

Just to back up what others said: Docker is designed to run containers based on images, so any changes to files need to be watched actively in development. If your hot reloading isn't working, it's often due to configuration issues or how the commands are set in your Dockerfile. If you're unsure, check how your app reacts to changes when not using Docker. It might also help to look into using a tool like Nodemon if you're using plain Node.js to ensure it picks up file changes.