nodejs应用程序以守护进程daemon的方式启动，容器化部署的时候一直部署出错，导致无法成功启动程序。

news2024/11/17 16:25:04

一、背景

nodejs应用程序使用Egg.js 框架脚本命令，见package.json：
在这里插入图片描述

"scripts": {
    "debug": "egg-bin debug",
    "clean": "easy clean",
    "build": "easy build prod",
    "start": "egg-scripts start --daemon --port=5174",
    "dev": "egg-bin dev --port 4000",
    "lint": "eslint .",
    "stop": "egg-scripts stop",
    "fix": "eslint --fix .",
    "ii": "npm install --registry https://registry.npm.taobao.org"
  },

egg-scripts start --daemon --port=5174 命令中的 --daemon 参数通常用于将应用程序以守护进程的方式启动，即在后台运行。

当使用ecs部署的时候，程序运行正常。
可是，当容器化之后，启动未见错误日志，但是容器一会儿就挂了。

二、问题描述

1、非容器启动程序

需要以守护进程的方式启动程序，故增加–daemon 参数启动。

> npm start

> player_egg@1.0.0 start
> egg-scripts start --daemon --port=5174

[egg-scripts] Starting egg application at /home/xxx/Documents/code/webPlayer
[egg-scripts] Run node /home/xxx/Documents/code/webPlayer/node_modules/egg-scripts/lib/start-cluster {"port":5174,"baseDir":"/home/xxx/Documents/code/webPlayer","framework":"/home/xxx/Documents/code/webPlayer/node_modules/egg","title":"egg-server-player_egg"} --title=egg-server-player_egg
[egg-scripts] Save log file to /home/xxx/logs
[egg-scripts] Wait Start: 1...
[egg-scripts] egg started on http://127.0.0.1:5174

在这里插入图片描述
可以看到，程序进程启动成功！

在这里插入图片描述

2、容器启动程序

这里省去如何制作docker容器的详细过程。

docker run -it --name=webplay -p 5174:5174 -v /home/xxx/Documents/code/webPlayer/log:/root/logs xxx/webplay:1.0.0 /bin/sh

启动的时候对容器日志进行持久化，便于观察问题。

在这里插入图片描述

查看日志：

cat /home/xxx/Documents/code/webPlayer/log/master-stdout.log

2024-04-07 02:17:39,240 INFO 48 [egg:loader] Controller loaded: /opt/app/controller
2024-04-07 02:17:39,247 INFO 48 [egg:core] dump config after load, 4ms
2024-04-07 02:17:39,254 INFO 48 [egg-mongoose] starting...
2024-04-07 02:17:39,283 INFO 48 [egg:core:ready_stat] end ready task /opt/node_modules/egg-mongoose/lib/mongoose.js:49:9, remain ["/opt/node_modules/egg-watcher/lib/init.js:15:14","/opt/node_modules/egg-mongoose/lib/mongoose.js:91:7","/opt/node_modules/egg-core/lib/egg.js:303:10"]
2024-04-07 02:17:39,283 INFO 48 [egg:core:ready_stat] end ready task /opt/node_modules/egg-core/lib/egg.js:303:10, remain ["/opt/node_modules/egg-watcher/lib/init.js:15:14","/opt/node_modules/egg-mongoose/lib/mongoose.js:91:7"]
2024-04-07 02:17:39,289 INFO 48 [egg-mongoose] mongodb://192.168.50.12:50000/webplay connected successfully
2024-04-07 02:17:39,290 INFO 48 [egg-mongoose] instance[0] start successfully
2024-04-07 02:17:39,292 INFO 48 [egg:core:ready_stat] end ready task /opt/node_modules/egg-mongoose/lib/mongoose.js:91:7, remain ["/opt/node_modules/egg-watcher/lib/init.js:15:14"]
2024-04-07 02:17:39,294 INFO 48 [egg-watcher:application] watcher start success
2024-04-07 02:17:39,294 INFO 48 [egg:core:ready_stat] end ready task /opt/node_modules/egg-watcher/lib/init.js:15:14, remain []
2024-04-07 02:17:39,306 INFO 29 [master] app_worker#2:48 started at 5174, remain 0 (2337ms)
2024-04-07 02:17:39,307 INFO 29 [master] egg started on http://127.0.0.1:5174 (2982ms)