You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run the docker image with Kubernetes and have RTL-Config.json punched in from a ConfigMap - this makes it always read-only. Here is how a startup attempt looks then:
│ [8/9/2024, 5:39:35 AM] ERROR: Config => Config file path: /etc/RTL/RTL-Config.json. │
│ │
│ [8/9/2024, 5:39:35 AM] ERROR: Config => Something went wrong while configuring the node server: │
│ Error: EROFS: read-only file system, open '/etc/RTL/RTL-Config.json'. │
│ │
│ file:///RTL/backend/utils/config.js:395 │
│ throw new Error(err); │
│ ^ │
│ │
│ Error: Error: EROFS: read-only file system, open '/etc/RTL/RTL-Config.json' │
│ at ConfigService.setServerConfiguration (file:///RTL/backend/utils/config.js:395:23) │
│ at new ConfigService (file:///RTL/backend/utils/config.js:398:14) │
│ at file:///RTL/backend/utils/config.js:401:23 │
│ at ModuleJob.run (node:internal/modules/esm/module_job:262:25) │
│ at async ModuleLoader.import (node:internal/modules/esm/loader:474:24) │
│ at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:109:5) │
│ │
│ Node.js v22.3.0
To Reproduce
Steps to reproduce the behavior:
take v0.15.2 from somewhere, ie. the docker image
make RTL-Config.json read-only one way or the other
observe it not to start
Your environment
Version of RTL v0.15.2 and 0.15.1 presumably, last working one is 0.15.0
Describe the bug
I run the docker image with Kubernetes and have RTL-Config.json punched in from a
ConfigMap
- this makes it always read-only. Here is how a startup attempt looks then:To Reproduce
Steps to reproduce the behavior:
Your environment
RTL
v0.15.2 and 0.15.1 presumably, last working one is 0.15.0The text was updated successfully, but these errors were encountered: