Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v0.15.2 fails to start on read-only RTL-Config.json #1435

Open
cvx35isl opened this issue Aug 9, 2024 · 0 comments
Open

v0.15.2 fails to start on read-only RTL-Config.json #1435

cvx35isl opened this issue Aug 9, 2024 · 0 comments
Assignees

Comments

@cvx35isl
Copy link

cvx35isl commented Aug 9, 2024

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:

│ [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:

  1. take v0.15.2 from somewhere, ie. the docker image
  2. make RTL-Config.json read-only one way or the other
  3. observe it not to start

Your environment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants