influxdata / influxdata/influxdata-docker
Influxdb Docker creates Volume
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 364
- Forks
- 255
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 7
Description
Hi
When I run the docker container for InfluxDB I mount two volumes with it. It looks something like this:
docker run -d \
--name influxdb \
--restart always \
--network bridge \
-v /${DOCKER_INSTALL_DIR}/influx/data:/var/lib/influxdb2 \
-v /${DOCKER_INSTALL_DIR}/influx/config/config.yml:/etc/influxdb2/config.yml \
-p 8086:8086 \
influxdb:2.0.7:latest
But the Image always creates also a volume and mount's it, even I didn't create the volume or even mount it. Is there a way to prevent the docker image from doing this?
The Volume look's like this:
Mount path: /var/lib/docker/volumes/8720d57/_data
Mounted At: /etc/influxdb2
Inside the Volume is an empty "config.yml"
I don't know if this is my configuration fault or if it's a fault by the docker image.
Every time I create a new container from this image, it creates a new volume.
Thank you for your help.
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
Reproduce the reported docker run command with influxdb:2.0.7:latest and inspect the resulting container mounts and image metadata. Determine whether the extra /etc/influxdb2 volume is intentional or unexpected; done means the behavior is corrected or clearly documented, with the reproduction result captured.
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
- Mostly clear
- Newbie friendliness
- 40/100