influxdata / influxdata/influxdata-docker
Consider removing VOLUMES from kapacitor Dockerfile
- Dominant language
- Shell
- Stars
- 364
- Forks
- 255
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 7
Description
Our use case does not require persisting the Kapacitor bolt DB outside the container. Our security requirements also require running the container as a non-root UID/GID. The VOLUMES declaration in the Dockerfile causes a volume mount owned by root which requires further workarounds.
If your image omits VOLUMES, then the image should be more flexible for downstream users.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the Kapacitor Dockerfile and inspect its VOLUMES declaration. Remove that declaration and verify that the resulting image does not force a root-owned volume mount, while remaining usable for downstream users that need their own persistence setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100