influxdata / influxdata/influxdata-docker
InfluxDB v2 requires unnecessary rw access to config
Open
Nobody has claimed this yet.
influxdb
- Dominant language
- Shell
- Stars
- 364
- Forks
- 255
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 7
Description
See https://github.com/influxdata/influxdata-docker/issues/492#issuecomment-855691078. InfluxDB v2 needs write-access to the config mount in order to run `influxd upgrade`, but it shouldn't need write-access when running in other modes.
Contributor guide
No contributing guide indexed for this repository
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 reading the linked issue comment and inspecting the Docker image configuration that controls the InfluxDB config mount. Done means `influxd upgrade` can write to the config mount while other operating modes do not require write access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100