NestJS 和 docker-compose 構建時出錯，找不到主文件

Question

所以我一直在使用使用 docker compose 和 Typescript 的 NestJS 應用程序。 直到最近我才遇到任何問題，現在每次我執行docker-compose build myApp和docker-compose up myApp時，容器都會失敗並顯示以下錯誤消息：

我已經嘗試了一些方法來解決這個問題，例如我刪除了容器和圖像，然后使用docker-compose build --no-cache myApp再次重建它，但這沒有用。 我不知道為什么有時它會起作用，但大多數時候它不起作用。 在我看來，這是一個隨機的結果，我不知道在刪除容器和圖像后是否應該等待更長時間才能使其正常工作。 我認為問題在於 Nest 構建沒有正確完成。 我需要找到一種方法來解決這個問題，因為我真的花了很多時間試圖找到解決方案。

這是我的 dockerfile 和我的 package.json。

Dockerfile

FROM node:14.17.0-alpine

WORKDIR /tmp

COPY . .

RUN npm install

RUN npm run build

EXPOSE 3005

ENV NODE_TLS_REJECT_UNAUTHORIZED=0

# Run it
ENTRYPOINT ["node", "/tmp/dist/main"]

package.json

{
  "name": "carbon-api",
  "private": true,
  "version": "0.2.1",
  "description": "",
  "license": "UNLICENSED",
  "scripts": {
    "prebuild": "rimraf dist",
    "build": "nest build",
    "format": "prettier --write \"src/**/*.ts\" \"test/**/*.ts\"",
    "start": "nest start",
    "start:dev": "nest start --watch",
    "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 --no-cache",
    "test:export": "jest --coverage && jest-coverage-to-csv ./coverage/api-sumary.json ./coverage/api-sumary.csv",
    "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": {
    "@casl/ability": "^5.2.2",
    "@grpc/proto-loader": "^0.5.6",
    "@nestjs/common": "^7.5.1",
    "@nestjs/core": "^7.5.1",
    "@nestjs/jwt": "^7.2.0",
    "@nestjs/microservices": "^7.2.0",
    "@nestjs/passport": "^7.1.5",
    "@nestjs/platform-express": "^7.5.1",
    "@nestjs/swagger": "^4.5.10",
    "@nestjs/typeorm": "^7.1.0",
    "@types/bcrypt": "^3.0.0",
    "aws-sdk": "^2.955.0",
    "bcryptjs": "^2.4.3",
    "body-parser": "^1.19.0",
    "body-parser-xml": "^2.0.0",
    "class-transformer": "^0.4.0",
    "class-validator": "^0.13.1",
    "dotenv": "^8.2.0",
    "grpc": "^1.24.4",
    "mysql": "^2.18.1",
    "nest-access-control": "^2.0.2",
    "nest-winston": "^1.3.5",
    "passport": "^0.4.1",
    "passport-jwt": "^4.0.0",
    "passport-local": "^1.0.0",
    "redis": "^3.0.2",
    "reflect-metadata": "^0.1.13",
    "rimraf": "^3.0.2",
    "rxjs": "^6.6.3",
    "swagger-ui-express": "^4.1.4",
    "typeorm": "^0.2.31",
    "winston": "^3.3.3"
  },
  "devDependencies": {
    "@nestjs/cli": "^7.5.1",
    "@nestjs/schematics": "^7.1.3",
    "@nestjs/testing": "^7.5.1",
    "@types/express": "^4.17.8",
    "@types/jest": "^26.0.15",
    "@types/multer": "^1.4.7",
    "@types/node": "^14.14.6",
    "@types/passport-jwt": "^3.0.4",
    "@types/passport-local": "^1.0.33",
    "@types/supertest": "^2.0.10",
    "@typescript-eslint/eslint-plugin": "^4.6.1",
    "@typescript-eslint/parser": "^4.6.1",
    "eslint": "^7.12.1",
    "eslint-config-prettier": "^6.15.0",
    "eslint-plugin-prettier": "^3.1.4",
    "jest": "^26.6.3",
    "prettier": "^2.1.2",
    "supertest": "^6.0.0",
    "ts-jest": "^26.4.3",
    "ts-loader": "^8.0.8",
    "ts-node": "^9.0.0",
    "tsconfig-paths": "^3.9.0",
    "typescript": "^4.0.5",
    "jest-coverage-to-csv": "^1.1.0"
  },
  "jest": {
    "moduleFileExtensions": [
      "js",
      "json",
      "ts"
    ],
    "coveragePathIgnorePatterns": [
      ".module.ts",
      ".config.ts",
      "main.ts",
      ".entity.ts",
      ".dto.ts",
      ".enum.ts",
      "constants.ts",
      "paginationParams.ts"
    ],
    "rootDir": "src",
    "testRegex": ".*\\.spec\\.ts$",
    "transform": {
      "^.+\\.(t|j)s$": "ts-jest"
    },
    "collectCoverageFrom": [
      "**/*.(t|j)s"
    ],
    "coverageDirectory": "../coverage",
    "coverageReporters": [
      [
        "json-summary",
        {
          "file": "api-sumary.json"
        }
      ],
      "html"
    ],
    "testEnvironment": "node"
  }
}

Answer 1

因此，對於那里的任何人，也許它很有用。

問題是我決定運行npm install以便能夠在我的本地機器上運行單元測試。 這對我的package-lock.json文件進行了一些更改，這在 docker 的構建過程中導致了此問題（如果我沒有添加新的依賴項，我不知道為什么要對其進行更改）。

我注意到它是因為 git 顯示此文件已修改，而它應該與上次保持相同。

無論哪種方式，我的解決方案是 go 到我項目的先前工作版本，復制舊的 package-lock.json 和瞧，解決了這個問題。