卷在 Docker 中不起作用。更准确地说，在 Nest.js 项目中跟踪文件更改不起作用

我正在使用 Docker 版本 20.10.21，构建 baeda1f。操作系统 Windows 11。决定在 Nest.js 上“dockerize”该应用程序。我通过 nest cli 创建了一个空项目并安装了 nodemon，虽然这里基本上不需要它，但没有它跟踪也可以工作。应用程序运行正常，一切正常。然后我决定创建一个 Docker 镜像和一个基于它的容器。这是我的Dockerfile

FROM node:latest

WORKDIR /app

RUN npm install -g nodemon

COPY package.json .

RUN npm install

COPY . .

EXPOSE 3030

CMD ["npm", "run", "start:dev"]

这是我的package.json

{
  "name": "nest_docker_setup",
  "version": "0.0.1",
  "description": "",
  "author": "",
  "private": true,
  "license": "UNLICENSED",
  "scripts": {
    "build": "nest build",
    "format": "prettier --write \"src/**/*.ts\" \"test/**/*.ts\"",
    "start": "nest start",
    "start:dev": "nodemon --config nodemon.json",
    "start:debug": "nest start --debug --watch",
    "start:prod": "node dist/main",
    "lint": "eslint \"{src,apps,libs,test}/**/*.ts\" --fix",
    "test": "jest",
    "test:watch": "jest --watch",
    "test:cov": "jest --coverage",
    "test:debug": "node --inspect-brk -r tsconfig-paths/register -r ts-node/register node_modules/.bin/jest --runInBand",
    "test:e2e": "jest --config ./test/jest-e2e.json"
  },
  "dependencies": {
    "@nestjs/common": "^11.0.1",
    "@nestjs/core": "^11.0.1",
    "@nestjs/platform-express": "^11.0.1",
    "reflect-metadata": "^0.2.2",
    "rxjs": "^7.8.1"
  },
  "devDependencies": {
    "@eslint/eslintrc": "^3.2.0",
    "@eslint/js": "^9.18.0",
    "@nestjs/cli": "^11.0.0",
    "@nestjs/schematics": "^11.0.0",
    "@nestjs/testing": "^11.0.1",
    "@swc/cli": "^0.6.0",
    "@swc/core": "^1.10.7",
    "@types/express": "^5.0.0",
    "@types/jest": "^29.5.14",
    "@types/node": "^22.10.7",
    "@types/supertest": "^6.0.2",
    "eslint": "^9.18.0",
    "eslint-config-prettier": "^10.0.1",
    "eslint-plugin-prettier": "^5.2.2",
    "globals": "^15.14.0",
    "jest": "^29.7.0",
    "nodemon": "^3.1.9",
    "prettier": "^3.4.2",
    "source-map-support": "^0.5.21",
    "supertest": "^7.0.0",
    "ts-jest": "^29.2.5",
    "ts-loader": "^9.5.2",
    "ts-node": "^10.9.2",
    "tsconfig-paths": "^4.2.0",
    "typescript": "^5.7.3",
    "typescript-eslint": "^8.20.0"
  },
  "jest": {
    "moduleFileExtensions": [
      "js",
      "json",
      "ts"
    ],
    "rootDir": "src",
    "testRegex": ".*\\.spec\\.ts$",
    "transform": {
      "^.+\\.(t|j)s$": "ts-jest"
    },
    "collectCoverageFrom": [
      "**/*.(t|j)s"
    ],
    "coverageDirectory": "../coverage",
    "testEnvironment": "node"
  }
}

main.ts 如下所示

import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';

async function bootstrap() {
  const app = await NestFactory.create(AppModule);
  await app.listen(process.env.PORT ?? 3030);
}
bootstrap();

这就是我的app.service.ts文件的样子

import { Injectable } from '@nestjs/common';

@Injectable()
export class AppService {
  getHello(): string {
    return 'Hello World!2';
  }
}

这就是我创建图像的方式

docker build -t server-nest:v1.0 .

这就是我创建容器的方法

docker run --name test-nest2 -p 3002:3030 --rm -v C:\Users\Dmitrij\work\nest_docker_setup:/app -v /app/node_modules server-nest:v1.0

绝对路径是正确的。这是应用程序的文件结构

究竟问题是什么？图像和容器已创建，但变更跟踪不起作用。那些。如果我更改 app.service.ts 文件中的行 return 'Hello World!2';然后通过 GET 请求 http://localhost:3002 我获得了之前的值。但即使没有 Docker，一切仍然正常。我想尝试安装 nodemon 并看看它是否可以工作，但是它没有工作。我尝试在容器运行时检查 nodemon 是否以这种方式安装。在 Docker 容器内，我运行命令来检查 nodemon 是否看到更改：

docker exec -it test-nest2 sh
nodemon --watch src --exec "nest start --watch"

我在控制台中收到了这个响应

[2:08:59 PM] Starting compilation in watch mode...

[2:09:01 PM] Found 0 errors. Watching for file changes.

[Nest] 99  - 02/23/2025, 2:09:01 PM     LOG [NestFactory] Starting Nest application...
[Nest] 99  - 02/23/2025, 2:09:01 PM     LOG [InstanceLoader] AppModule dependencies initialized +8ms
[Nest] 99  - 02/23/2025, 2:09:01 PM     LOG [RoutesResolver] AppController {/}: +3ms
[Nest] 99  - 02/23/2025, 2:09:01 PM     LOG [RouterExplorer] Mapped {/, GET} route +2ms
[Nest] 99  - 02/23/2025, 2:09:01 PM     LOG [NestApplication] Nest application successfully started +1ms
[Nest] 99  - 02/23/2025, 2:09:01 PM   ERROR [NestApplication] Error: listen EADDRINUSE: address already in use :::3030 +2ms
node:net:1937
    const ex = new UVExceptionWithHostPort(err, 'listen', address, port);
               ^

Error: listen EADDRINUSE: address already in use :::3030
    at Server.setupListenHandle [as _listen2] (node:net:1937:16)
    at listenInCluster (node:net:1994:12)
    at Server.listen (node:net:2099:7)
    at ExpressAdapter.listen (/app/node_modules/@nestjs/platform-express/adapters/express-adapter.js:109:32)
    at /app/node_modules/@nestjs/core/nest-application.js:183:30
    at new Promise (<anonymous>)
    at NestApplication.listen (/app/node_modules/@nestjs/core/nest-application.js:173:16)
    at async bootstrap (/app/src/main.ts:6:3) {
  code: 'EADDRINUSE',
  errno: -98,
  syscall: 'listen',
  address: '::',
  port: 3030
}

Node.js v23.8.0
PS C:\Users\Dmitrij\work\nest_docker_setup> 

我尝试更改端口，但没有什么帮助。我希望有人能提出一些建议。