Influxdb pod is going in crashloopbackoff state

InfluxDB 2
1

I have deployed influxdb oss in openshift using the helm chart here: helm-charts/charts/influxdb2 at master · influxdata/helm-charts · GitHub.

But my pod is going in crashloopbackoff state with error

chmod: /var/lib/influxdb2: Operation not permitted

3chmod: /etc/influxdb2: Operation not permitted

4{

5"bolt-path": “/var/lib/influxdb2/influxd.bolt”,

6"engine-path": “/var/lib/influxdb2/engine”,

7"nats-port": 4222,

8"http-bind-address": “:9999”

9}

102024-08-16T10:58:16. info booting influxd server in the background {“system”: “docker”}

11ts=2024-08-16T10:58:16.609285Z lvl=info msg=“Welcome to InfluxDB” log_id=0r2iFodG000 version=v2.7.4 commit=19e5c0e1b7 build_date=2023-11-08T17:07:39Z log_level=info

12ts=2024-08-16T10:58:16.609335Z lvl=warn msg=“nats-port argument is deprecated and unused” log_id=0r2iFodG000

13ts=2024-08-16T10:58:16.613784Z lvl=info msg=“Resources opened” log_id=0r2iFodG000 service=bolt path=/var/lib/influxdb2/influxd.bolt

14ts=2024-08-16T10:58:16.613904Z lvl=info msg=“Resources opened” log_id=0r2iFodG000 service=sqlite path=/var/lib/influxdb2/influxd.sqlite

15ts=2024-08-16T10:58:16.615025Z lvl=info msg=“Bringing up metadata migrations” log_id=0r2iFodG000 service=“KV migrations” migration_count=20

16ts=2024-08-16T10:58:16.738639Z lvl=info msg=“Bringing up metadata migrations” log_id=0r2iFodG000 service=“SQL migrations” migration_count=8

17ts=2024-08-16T10:58:16.819741Z lvl=info msg=“Using data dir” log_id=0r2iFodG000 service=storage-engine service=store path=/var/lib/influxdb2/data

18ts=2024-08-16T10:58:16.820282Z lvl=info msg=“Compaction settings” log_id=0r2iFodG000 service=storage-engine service=store max_concurrent_compactions=16 throughput_bytes_per_second=50331648 throughput_bytes_per_second_burst=50331648

19ts=2024-08-16T10:58:16.820294Z lvl=info msg=“Open store (start)” log_id=0r2iFodG000 service=storage-engine service=store op_name=tsdb_open op_event=start

20ts=2024-08-16T10:58:16.821328Z lvl=info msg=“Open store (end)” log_id=0r2iFodG000 service=storage-engine service=store op_name=tsdb_open op_event=end op_elapsed=1.035ms

21ts=2024-08-16T10:58:16.821364Z lvl=info msg=“Starting retention policy enforcement service” log_id=0r2iFodG000 service=retention check_interval=30m

22ts=2024-08-16T10:58:16.821372Z lvl=info msg=“Starting precreation service” log_id=0r2iFodG000 service=shard-precreation check_interval=10m advance_period=30m

23ts=2024-08-16T10:58:16.826228Z lvl=info msg=“Starting query controller” log_id=0r2iFodG000 service=storage-reads concurrency_quota=1024 initial_memory_bytes_quota_per_query=9223372036854775807 memory_bytes_quota_per_query=9223372036854775807 max_memory_bytes=0 queue_size=1024

24ts=2024-08-16T10:58:16.829099Z lvl=info msg=“Configuring InfluxQL statement executor (zeros indicate unlimited).” log_id=0r2iFodG000 max_select_point=0 max_select_series=0 max_select_buckets=0

25ts=2024-08-16T10:58:16.836394Z lvl=info msg=Starting log_id=0r2iFodG000 service=telemetry interval=8h

26ts=2024-08-16T10:58:16.836489Z lvl=info msg=Listening log_id=0r2iFodG000 service=tcp-listener transport=http addr=:9999 port=9999

272024-08-16T10:58:17. info pinging influxd… {“system”: “docker”, “ping_attempt”: “0”}

282024-08-16T10:58:17. info got response from influxd, proceeding {“system”: “docker”, “total_pings”: “1”}

29Error: setup succeeded, but failed to write new config to local path: open /etc/influxdb2/influx-configs: permission denied

302024-08-16T10:58:17. warn cleaning bolt and engine files to prevent conflicts on retry {“system”: “docker”, “bolt_path”: “/var/lib/influxdb2/influxd.bolt”, “engine_path”: “/var/lib/influxdb2”}

these are my env var

env:
- name: DOCKER_INFLUXDB_INIT_MODE
value: setup
- name: DOCKER_INFLUXDB_INIT_USERNAME
value: admin
- name: DOCKER_INFLUXDB_INIT_PASSWORD
valueFrom:
secretKeyRef:
name: test-influxdb2-auth
key: admin-password
- name: DOCKER_INFLUXDB_INIT_ORG
value: influxdata
- name: DOCKER_INFLUXDB_INIT_BUCKET
value: default
- name: DOCKER_INFLUXDB_INIT_RETENTION
value: 0s
- name: DOCKER_INFLUXDB_INIT_ADMIN_TOKEN
valueFrom:
secretKeyRef:
name: test-influxdb2-auth
key: admin-token
- name: INFLUXD_BOLT_PATH
value: /var/lib/influxdb2/influxd.bolt
- name: INFLUXD_ENGINE_PATH
value: /var/lib/influxdb2
how to resolve this??

2

Hello @Rishav_Kumar_Jha,
Have you tried updating the yaml?

securityContext:
  enabled: true
  runAsUser: 1000
  fsGroup: 1000

to modify the security context to allow the container to run with elevated privileges or allow it to run as a non-root user with appropriate permissions?

If this doesn’t work I’d love to encouraging to file an issue on gh.