- The involved route, with all required and optional parameters
N/A
- What is expected
Latest docker image 2021-08-12 runs without an error.
- What is actually happening
Throws error at start:
> rsshub@1.0.0 start /app
> node lib/index.js
internal/modules/cjs/loader.js:892
throw err;
^
Error: Cannot find module 'module-alias'
Require stack:
- /app/lib/app.js
- /app/lib/index.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:889:15)
at Function.Module._load (internal/modules/cjs/loader.js:745:27)
at Module.require (internal/modules/cjs/loader.js:961:19)
at require (internal/modules/cjs/helpers.js:92:18)
at Object.<anonymous> (/app/lib/app.js:1:21)
at Module._compile (internal/modules/cjs/loader.js:1072:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
at Module.load (internal/modules/cjs/loader.js:937:32)
at Function.Module._load (internal/modules/cjs/loader.js:778:12)
at Module.require (internal/modules/cjs/loader.js:961:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [ '/app/lib/app.js', '/app/lib/index.js' ]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! rsshub@1.0.0 start: `node lib/index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the rsshub@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-08-12T22_31_13_401Z-debug.log
- Self-deployment information
| Env |
Value |
| OS |
Ubuntu 20.04 & 21.04 |
| Node version |
|
| if Docker, version |
podman 3.2.3 |
- Additional info (logs errors etc)
I am using podman to run the container/compose file, but the same error does not appear in 2021-07-13 with the same set up. It seems to be a docker image issue. Feel free to test with "proper" docker setup.
N/A
Latest docker image
2021-08-12runs without an error.Throws error at start:
podman3.2.3I am using
podmanto run the container/compose file, but the same error does not appear in2021-07-13with the same set up. It seems to be a docker image issue. Feel free to test with "proper" docker setup.