Error configuring opensearch.yml - Read-only file system

[FelipeAFV]

Name and Version

bitnami/opensearch 1.2.9

What architecture are you using?

None

What steps will reproduce the bug?

In chart version 1.2.9. And opensearch version2.15.0.

I tried to apply the following config to enable the security plugin.

opensearch:
  config:
    plugins:
      security:
        disabled: "false"

Then when I install or do a reconfigure I get the following error:

Defaulted container "opensearch" out of: opensearch, sysctl (init), copy-default-plugins (init), k8tz (init)
opensearch 14:56:06.96 INFO  ==>
opensearch 14:56:06.96 INFO  ==> Welcome to the Bitnami opensearch container
opensearch 14:56:06.96 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
opensearch 14:56:06.96 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
opensearch 14:56:06.97 INFO  ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
opensearch 14:56:06.97 INFO  ==>
opensearch 14:56:07.06 INFO  ==> ** Starting Opensearch setup **
opensearch 14:56:07.12 INFO  ==> Configuring/Initializing Opensearch...
opensearch 14:56:07.17 INFO  ==> Custom configuration file detected, using it...
cp: cannot create regular file '/opt/bitnami/opensearch/config/opensearch.yml': Read-only file system

What is the expected behavior?

I expect to opensearch.yml be modified in the pods, resulting in the security plugin being enabled

[carrodher]

Could you please check the permissions of the directory (in the host) where the volume is mounted?

Bitnami containers are designed to operate as non-root by default. Consequently, any files or directories used by the application should be owned by the root group, as the random user (1001 by default) is a member of this root group. To ensure proper permissions, you'll need to adjust the ownership of your local directory accordingly.

For more comprehensive information about non-root containers and their significance for security, you can explore the following resources:

• Why non-root containers are important for security
• Use Non-Root Containers
• Work With Non-Root Containers for Bitnami Applications
• Running non-root containers on Openshift

These references provide valuable insights into the best practices and considerations when working with non-root containers in Bitnami applications.