我在将我的Node.js项目进行Docker化时遇到了错误。

huangapple
go评论97阅读模式
英文:

I get an error while dockerizing my nodejs project

问题

I am trying to dockerize an application for a project. I'm using node.js as my server. In the process of dockerizing it throws this error:

  1. cloud_project2-projectapp-1           | npm ERR! code ENOENT
  2. cloud_project2-projectapp-1           | npm ERR! syscall open
  3. cloud_project2-projectapp-1           | npm ERR! path /projectapp/package.json
  4. cloud_project2-projectapp-1           | npm ERR! errno -2
  5. cloud_project2-projectapp-1           | npm ERR! enoent ENOENT: no such file or directory, open '/projectapp/package.json'
  6. cloud_project2-projectapp-1           | npm ERR! enoent This is related to npm not being able to find a file.
  7. cloud_project2-projectapp-1           | npm ERR! enoent

This is my Dockerfile:

  1. FROM node:18-alpine
  2. WORKDIR /projectapp
  3. COPY package*.json .
  4. RUN npm ci
  5. COPY . .
  6. ENV PORT=8080
  7. EXPOSE 8080
  8. CMD ["npm", "run", "devStart"]

The dockerfile is exactly as I've seen in many videos and in the documentation. I believe the error is thrown in the RUN npm ci command and for some reason it cannot find the package.json file even though I copy it in the above command. I also searched for some answers and maybe it's a privileges issue, but I'm new to Linux and have a hard time understanding these.

I get a couple more errors with MySQL and Keyrock, but I'll debug these later.

  1. version: "3.9"
  3. networks:
  4.   idm_network:
  5.     driver: bridge
  7. # Project images
  8. services:
  9.   projectapp:
  10.      build:
  11.        context: ./projectapp
  12.      networks:
  13.        - idm_network
  14.      volumes:    
  15.       - .:/projectapp   # for development phase only
  16.      ports:
  17.        - "8080:8080"  
  19.   mysql:
  20.       build:
  21.         context: ./mysql
  22.       networks:
  23.         - idm_network
  24.       volumes:
  25.         - project-mysql-data:/var/lib/mysql
  26.       environment:
  27.         - MYSQL_ROOT_PASSWORD=idm
  28.         - MYSQL_ROOT_HOST=%
  30.   keyrock:
  31.     image: fiware/idm:latest  
  32.     networks:
  33.         - idm_network
  34.     depends_on:
  35.         - mysql
  36.     environment:
  37.         - IDM_DB_HOST=mysql
  39.   mongo-orion:
  40.     image: mongo:latest
  41.     volumes:
  42.       - project-mongo-orion-data:/data/db
  43.     networks:
  44.       - idm_network
  45.     command: --nojournal
  47.   orion:
  48.     image: fiware/orion
  49.     links:
  50.      - mongo-orion
  51.     networks:
  52.       - idm_network
  53.     command: -dbhost mongo-orion
  55.   mongo-data:
  56.     build:
  57.       context: ./mongoData
  58.     volumes:
  59.       - project-mongo-data:/data/db
  60.     networks:
  61.       - idm_network
  63.   data-storage-server:
  64.     build:
  65.       context: ./dataStorageServer
  66.     volumes:   
  67.       - .:/dataserver  # for development phase only
  68.     depends_on:
  69.       - mongo-data
  70.     networks:
  71.       - idm_network
  73. # Project volumes
  74. volumes:
  75.   project-mysql-data:
  76.   project-mongo-orion-data:
  77.   project-mongo-data:
英文:

I am trying to dockerize an application for a project. I'm using node.js as my server. In the process of dockerizing it throws this error:

  1. cloud_project2-projectapp-1           | npm ERR! code ENOENT
  2. cloud_project2-projectapp-1           | npm ERR! syscall open
  3. cloud_project2-projectapp-1           | npm ERR! path /projectapp/package.json
  4. cloud_project2-projectapp-1           | npm ERR! errno -2
  5. cloud_project2-projectapp-1           | npm ERR! enoent ENOENT: no such file or directory, open '/projectapp/package.json'
  6. cloud_project2-projectapp-1           | npm ERR! enoent This is related to npm not being able to find a file.
  7. cloud_project2-projectapp-1           | npm ERR! enoent

This is my Dockerfile:

  1. FROM node:18-alpine
  2. WORKDIR /projectapp
  3. COPY package*.json .
  4. RUN npm ci
  5. COPY . .
  6. ENV PORT = 8080
  7. EXPOSE 8080
  8. CMD ["npm","run","devStart"]

The dockerfile is exactly as I've seen in many videos and in the documentation. I believe the error is thrown in the RUN npm ci command and for some reason it cannot find the package.json file even though I copy it in the above command. I also searched for some answers and maybe it's a priviledges issue, but I'm new to linux and have a hard time understanding these.

I get a couple more errors with mysql and keyrock, but I'll debug these later.

  1. version: "3.9"
  3. networks:
  4.   idm_network:
  5.     driver: bridge
  7. #project images
  8. services:
  9.   projectapp:
  10.      build:
  11.        context: ./projectapp
  12.      networks:
  13.        - idm_network
  14.      volumes:    
  15.       - .:/projectapp   #for development phase only
  16.      ports:
  17.        - "8080:8080"  
  19.   mysql:
  20.       build:
  21.         context:
  22.           ./mysql
  23.       networks:
  24.         - idm_network
  25.       volumes:
  26.         - project-mysql-data:/var/lib/mysql
  27.       environment:
  28.         - MYSQL_ROOT_PASSWORD=idm
  29.         - MYSQL_ROOT_HOST=%
  32.   keyrock:
  33.     image: fiware/idm:latest  
  34.     networks:
  35.         - idm_network
  36.     depends_on:
  37.         - mysql
  38.     environment:
  39.         - IDM_DB_HOST=mysql
  42.   mongo-orion:
  43.     image: mongo:latest
  44.     volumes:
  45.       - project-mongo-orion-data:/data/db
  46.     networks:
  47.       - idm_network
  48.     command: --nojournal
  50.   orion:
  51.     image: fiware/orion
  52.     links:
  53.      - mongo-orion
  54.     networks:
  55.       - idm_network
  56.     command: -dbhost mongo-orion
  58.   mongo-data:
  59.     build:
  60.       context: ./mongoData
  61.     volumes:
  62.       - project-mongo-data:/data/db
  63.     networks:
  64.       - idm_network
  66.   data-storage-server:
  67.     build:
  68.       context: ./dataStorageServer
  69.     volumes:   
  70.       - .:/dataserver  #for development phase only
  71.     depends_on:
  72.       - mongo-data
  73.     networks:
  74.       - idm_network
  76.   #pep-proxy-datastorage:
  77.   #  image: fiware/pep-proxy:latest
  78.   #  networks:
  79.   #    - idm_network
  81.   #pep-proxy-orion:
  82.   #image: fiware/pep-proxy:latest
  83.   #networks:
  84.   #  - idm_network
  86. #project volumes
  87. volumes:
  88.   project-mysql-data:
  89.   project-mongo-orion-data:
  90.   project-mongo-data:

答案1

得分: 0

删除 projectapp 下的 volumes: 块。

此块的作用是使用主机系统中的内容替换镜像中的整个应用程序。 （想象一下正常安装 Node，然后单独检出 Node 的源代码并解压缩到您已经安装的 Node 上。）没有特定的保证或检查镜像和主机内容是否"匹配"。像镜像中 npm install 的 node_modules 树等内容也会被隐藏。

在您的情况下，您正在从 ./projectapp 子目录构建镜像，但是在镜像代码上进行绑定挂载到当前目录 .，这会导致在运行容器时没有 package.json，从而产生您看到的错误。

我可能会对此设置进行两个更改。如果您删除文件中的所有 networks: 块，Compose 将创建一个名为 default 的网络并将所有容器附加到它；这将与您现在拥有的网络完全相同，但需要更少的设置。您还可以使用简写的 build: directoryname，其含义与您现在拥有的 build: { context: directoryname } 相同。这样做，再加上删除不必要的 volumes:，将使您的配置简化为：

  1. version: '3.8'
  3. services:
  4.   projectapp:
  5.     build: ./projectapp
  6.     ports:
  7.       - "8080:8080"  
  9.   ...
  11.   mongo-data:
  12.     build: ./mongoData
  13.     volumes:  # 保留卷以用于持久数据库数据
  14.       - project-mongo-data:/data/db
  16.   data-storage-server:
  17.     build: ./dataStorageServer
  18.     depends_on:
  19.       - mongo-data

orion 服务还具有已过时的 links: 选项，您也可以将其删除（或更改为 depends_on:）；名称 mongo-orion 仍然会使用正常的 Docker 网络解析。

英文:

Delete the volumes: block under projectapp.

What this block does is replace your entire application in the image with content from the host system. (Imagine installing a copy of Node normally, then separately checking out Node's source code and unpacking it over the installed Node you already have.) There's no particular guarantee or check that the image and the host content "match". Things like the node_modules tree that the image npm installs get hidden as well.

In your case, you're building the image out of a ./projectapp subdirectory, but bind-mounting the current directory . over the image code. That causes there to not be a package.json when you run the container, which produces the error you see.

I might make two more changes to this setup. If you delete all of the networks: blocks in the file, Compose will create a network named default and attach all of the containers to it; this will work exactly the same way as the network you have now, but require less setup. You can also use a shorthand build: directoryname which means the same as the build: { context: directoryname } you have now. That, plus deleting the unnecessary volumes:, would get you down to

  1. version: '3.8'
  3. services:
  4.   projectapp:
  5.     build: ./projectapp
  6.     ports:
  7.       - "8080:8080"  
  9.   ...
  11.   mongo-data:
  12.     build: ./mongoData
  13.     volumes:  # keep volumes for persistent database data
  14.       - project-mongo-data:/data/db
  16.   data-storage-server:
  17.     build: ./dataStorageServer
  18.     depends_on:
  19.       - mongo-data

The orion service also has the obsolete links: option and you can just delete that block as well (or change it to depends_on:); the name mongo-orion will still resolve using normal Docker networking.

答案2

得分: 0

问题是我有这行代码：

  1. volumes:
  2. - .:/projectapp   # 仅用于开发阶段

这样我就不必在每次进行更改时都重新启动 Docker，但这造成了问题。

英文:

Problem was I had this line:

  1. volumes:    
  2. - .:/projectapp   #for development phase only

so that I don't have to restart docker every time I made a change, but it created a problem.

huangapple
  • 本文由 发表于 2023年1月10日 18:28:52
  • 转载请务必保留本文链接：https://go.coder-hub.com/75068631.html
  • docker
  • docker-compose
  • dockerfile
  • node.js
  • npm-install
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定