[Workbench] Warning message during startup for `database.conf` mount
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
When database.conf is defined, the below warning is triggered during startup. The permissions are correct (root:root) and likely don't ever need an update in an k8s environment. I guess the check comes from an internal WB process but is likely only relevant for non-k8s envs?
Would be good to account for it as one cannot do so because the referenced mount is initiated by the chart. AFAICS this affects all deployments which don't use the built-in SQLITE DB.
config:
secret:
database.conf
provider: postgresql
2024-01-09T15:53:17.928385Z [rserver] WARNING Failed attempt to update ownership of database configuration file /mnt/secret-configmap/rstudio/database.conf to root user: Read-only file system - please ensur │
│ e that the file owner is root if it contains sensitive information; LOGGED FROM: rstudio::core::Error rstudio::server_core::database::{anonymous}::readOptions(const string&, const rstudio_boost::optional<rs │
│ tudio::core::system::User>&, rstudio::core::database::ConnectionOptions*, std::string) src/cpp/server_core/ServerDatabase.cpp:343
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the chart-managed database.conf mount and the warning reported from src/cpp/server_core/ServerDatabase.cpp:343. Reproduce startup with the PostgreSQL database.conf configuration, then determine how the read-only mount is handled; done means the deployment no longer emits this misleading warning while preserving the stated ownership check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100