influxdata / influxdata/influxdata-docker
Kapacitor volume mounting (docker)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 364
- Forks
- 255
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 7
Description
I am trying to run influxdb and kapacitor in Docker, based on the official influxdata containers on docker hub. Influxdb installs and runs fine. Kapacitor not. I am running on an mac with docker machine (latest, installed earlier this week without any issues)
Following the documented instruction, right after installation from docker hub, I start kapacitor:
$ docker run -p 9092:9092 kapacitor
this runs fine.
Next, I tried to mount a local volume (as documented in "how to use this image")
- create empty directory /Users/username/mydocker/kapacitor
- $docker run -p 9092:9092 -v /Users/username/mydocker/kapacitor:/var/lib/kapacitor kapacitor
This causes the error:
E! open server: open service *storage.Service: open boltdb @ "/var/lib/kapacitor/kapacitor.db": invalid argument
Now I am stuck. Can't figure out how to solve this error. Neither can I find any related solutions anywhere. Hope anyone can help me solve this issue.
Hans
PS: in my investigation I also discovered that the current Docker image is not fully up-to-date yet. It is running 1.2.0. As a maintainer on docker hub, would you please also update kapacitor (influxdb is fully up-to-date, kapacitor not)
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 reproducing the documented docker run command with the bind mount at /var/lib/kapacitor and compare it with the image configuration. Check the Kapacitor Docker image currently tagged in the repository against the reported 1.2.0 image. Done means the mounted container starts successfully and the published image is up to date if an image update is in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100