file_storage extension: permission denied

[yuzhouliu9]

Component(s)

extensions/file_storage

What happened?

Description

I'm trying to set up the s3 exporter with a persistent queue to avoid dropping logs when the otel collector pod dies

    exporters:
      awss3/devops:
        sending_queue:
          enabled: true
          num_consumers: 10
          queue_size: 10000
          storage: file_storage/otc

    extensions:
      file_storage/otc:
        directory: /otel-storage
        create_directory: true

    service:
      extensions: [file_storage/otc]

The collector pod has the correct volume and volumeMount, and the PVC exists

  volumeMounts:
    - name: otel-storage
      mountPath: /otel-storage
      readOnly: false
  volumes:
    - name: otel-storage
      persistentVolumeClaim:
        claimName: devops-otel-storage

But the collector pod exits with error

Error: cannot start pipelines: failed to start "awss3/devops" exporter: open /otel-storage/exporter_awss3_devops_logs: permission denied; failed to shutdown pipelines: no existing monitoring routine is running
2025/05/29 20:04:54 collector server run finished with error: cannot start pipelines: failed to start "awss3/devops" exporter: open /otel-storage/exporter_awss3_devops_logs: permission denied; failed to shutdown pipelines: no existing monitoring routine is running

I'm not sure what I'm missing in configuration to give it the proper permissions.

Steps to Reproduce

See description

Expected Result

file_storage extension should be able to write to mounted volume

Actual Result

file_storage extension results in permission denied

Collector version

0.126.0

Environment information

Environment

OS: Ubuntu 20.04

OpenTelemetry Collector configuration

Log output

Additional context

No response

[VihasMakwana]

@yuzhouliu9 hello!

Maybe try adding following in your k8s yaml

securityContext:
          fsGroup: 1001
          runAsUser: 1001
          runAsGroup: 1001

[github-actions]

Pinging code owners for extension/storage/filestorage: @swiatekm @VihasMakwana. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[henningploegerzeb]

Same issue here. The only differences:

• version 0.125.0
• loadbalancing exporter
• file storage as pv on Azure file share

First pod runs without problems. Scaling to 2 pods or performing a rolling update leads to the above described error for all added pods.

[swiatekm]

This doesn't look like a problem with the extension, but rather with permissions in the environment. @henningploegerzeb @yuzhouliu9 can you verify what the permissions on the volume you're creating are, and what user and group the otel collector is running as?

[yuzhouliu9]

Maybe try adding following in your k8s yaml

securityContext:
fsGroup: 1001
runAsUser: 1001
runAsGroup: 1001

Thank you so much! This solved it!