GCloud Run部署Node.js应用遇端口及node命令未找到问题求助

问题描述 #

在GCloud Run上部署Node.js应用时持续报错：
The user-provided container failed to start and listen on the port defined provided by the PORT=5000 environment variable

已调整端口变量与app.listen配置，确认监听逻辑正确，但日志中先出现警告bash: node: command not found。已在package.json的engines字段指定node: >=18.0.0，并在app.yaml中设置nodejs18，需排查遗漏的配置项。

服务启动代码 #

this.app.listen(process.env.PORT, () => {
    console.log(`Server Listening on port ${process.env.PORT}`);
});

GCloud YAML配置文件 #

apiVersion: serving.knative.dev/v1
kind: Service
metadata:
  name:
  namespace:
  selfLink: 
  resourceVersion: 
  generation: 14
  creationTimestamp: '2023-01-17T23:15:41.934438Z'
  labels:
    managed-by: gcp-cloud-build-deploy-cloud-run
    gcb-trigger-id: 
    commit-sha: 
    gcb-build-id: 
    cloud.googleapis.com/location: europe-west1
  annotations:
    run.googleapis.com/client-name: gcloud
    serving.knative.dev/creator:
    serving.knative.dev/lastModifier: 
    client.knative.dev/user-image:
    run.googleapis.com/client-version: 415.0.0
    run.googleapis.com/operation-id:
    run.googleapis.com/ingress: all
    run.googleapis.com/ingress-status: all
spec:
  template:
    metadata:
      name:
      labels:
        managed-by: gcp-cloud-build-deploy-cloud-run
        gcb-trigger-id:
        commit-sha:
        gcb-build-id:
      annotations:
        run.googleapis.com/client-name: gcloud
        client.knative.dev/user-image: 
        run.googleapis.com/client-version: 415.0.0
        autoscaling.knative.dev/maxScale: '100'
    spec:
      containerConcurrency: 80
      timeoutSeconds: 300
      serviceAccountName:
      containers:
      - image: 
        ports:
        - name: http1
          containerPort: 8080
        resources:
          limits:
            cpu: 1000m
            memory: 512Mi
  traffic:
  - percent: 100
    latestRevision: true
status:
  observedGeneration: 14
  conditions:
  - type: Ready
    status: 'False'
    reason: HealthCheckContainerError
    message: "Revision '' is not ready and cannot serve traffic. The\
      \ user-provided container failed to start and listen on the port defined provided\
      \ by the PORT=8080 environment variable. Logs for this revision might contain\
      \ more information.\n\nLogs URL: 
      \ \nFor more troubleshooting guidance, see https://cloud.google.com/run/docs/troubleshooting#container-failed-to-start"
    lastTransitionTime: '2023-01-26T12:36:36.279097Z'
  - type: ConfigurationsReady
    status: 'False'
    reason: HealthCheckContainerError
    message: "The user-provided container failed to start and listen on the port defined\
      \ provided by the PORT=8080 environment variable. Logs for this revision might contain\
      \ more information.\n\nLogs URL: 
      \ \nFor more troubleshooting guidance, see https://cloud.google.com/run/docs/troubleshooting#container-failed-to-start"
    lastTransitionTime: '2023-01-26T12:36:36.279097Z'
  - type: RoutesReady
    status: 'False'
    reason: HealthCheckContainerError
    message: "Revision '' is not ready and cannot serve traffic. The\
      \ user-provided container failed to start and listen on the port defined provided\
      \ by the PORT=8080 environment variable. Logs for this revision might contain\
      \ more information.\n\nLogs URL: 
      \ \nFor more troubleshooting guidance, see https://cloud.google.com/run/docs/troubleshooting#container-failed-to-start"
    lastTransitionTime: '2023-01-26T12:36:36.208550Z'
  latestReadyRevisionName: 
  latestCreatedRevisionName: 
  traffic:
  - revisionName: 
    percent: 100
    latestRevision: true
  url: 
  address:
    url: 

排查方向与修复方案 #

1. 确保容器镜像包含Node.js环境 #

bash: node: command not found是核心问题，端口报错是Node进程未启动导致的连锁反应：

• 若使用Cloud Build构建镜像，需在cloudbuild.yaml中明确使用Node.js 18的构建镜像：

  steps:
  - name: 'gcr.io/cloud-builders/npm:node-18'
    args: ['install']
  - name: 'gcr.io/cloud-builders/npm:node-18'
    args: ['run', 'build']
  - name: 'gcr.io/cloud-builders/docker'
    args: ['build', '-t', 'gcr.io/[你的项目ID]/[镜像名]', '.']
  images:
  - 'gcr.io/[你的项目ID]/[镜像名]'
  

• 若使用自定义Dockerfile，必须指定Node.js 18的基础镜像：

  FROM node:18-alpine
  WORKDIR /app
  COPY package*.json ./
  RUN npm install
  COPY . .
  EXPOSE ${PORT:-8080}
  CMD ["npm", "start"]
  

2. 验证启动命令有效性 #

• 检查package.json的scripts.start字段，确保指向正确的入口文件，例如："start": "node server.js"
• 若在Cloud Run配置中手动指定启动命令，需确保命令路径正确，优先使用npm start（需package.json配置正常）

3. 统一端口配置 #

• 从YAML配置看，容器端口设为8080，Cloud Run默认会将PORT环境变量设为8080，需确保代码中process.env.PORT读取的是该值，避免硬编码5000
• 保证YAML中的containerPort与PORT环境变量值一致

4. 注意app.yaml的适用范围 #

app.yaml中的nodejs18配置仅对App Engine有效，Cloud Run不读取该文件的运行时配置，必须通过镜像或Cloud Build指定Node.js版本

5. 本地测试镜像可用性 #

在本地构建并运行镜像，验证是否能正常启动：

docker build -t my-node-app .
docker run -p 8080:8080 -e PORT=8080 my-node-app

若本地也出现node: command not found，需先修复镜像问题再部署

内容的提问来源于stack exchange，提问作者Alarm-1202