influxdata / influxdata/influxdata-docker
Unable to start influxdb3-core the container from scratch (Debian)
- Dominant language
- Shell
- Stars
- 364
- Forks
- 255
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 7
Description
With reference to https://community.influxdata.com/t/error-running-influxdb3-core-docker-container-on-ubuntu-24-04/58040/10
I Followed the instruction to create a docker compose file as shown in https://hub.docker.com/_/influxdb
When I run docker compose up I get this error :
`influxdb3-core: Serve command failed: failed to initialize catalog: object store error: ObjectStore(Generic { store: "LocalFileSystem", source: UnableToCreateDir { source: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }, path: "/var/lib/influxdb3/data/node0/catalog/v2" } })
`
Instead of binding the volume to my filesystem, I created a named volume (see docker compose file bellow)
Same error occured.
I entered into the volume manually with an other container as "[lmaddox]" suggested int he forum and created the "/var/lib/influxdb3" folder and changed the ownership of this folder to "chown -vR 1500:1500 /var/lib/influxdb3"
After that I recreated the container and everything was going well.
Please consider adding the folder creation in the dockerfile
```yaml
# compose.yaml
name: influxdb3
services:
influxdb3-core:
container_name: influxdb3-core
image: influxdb:3-core
ports:
- 8181:8181
command:
- influxdb3
- serve
- --node-id=node0
- --object-store=file
- --data-dir=/var/lib/influxdb3/data
- --plugin-dir=/var/lib/influxdb3/plugins
volumes:
- influx-data:/var/lib/influxdb3/data
- influx-plugins:/var/lib/influxdb3/plugins
restart: always
volumes:
influx-plugins:
influx-data:
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the compose.yaml configuration in the issue and inspect the Dockerfile used for the influxdb:3-core image, focusing on initialization of /var/lib/influxdb3 and ownership for UID 1500. Reproduce with the shown Docker Compose setup; done means a fresh named-volume deployment starts without manually creating or chowning the directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100