Skip to content

[BUG][OpenSearchDashboards] OpenSearch Dashboards fails to start when readOnlyRootFilesystem set to 'true' #368

@gsmith-sas

Description

@gsmith-sas

Describe the bug
When I set the readOnlyRootFilesystem key to 'true', the OpenSearch Dashboards pod cannot be started. The following messages appear in the pod log:

FATAL Error: Unable to write OpenSearch Dashboards UUID file, please check the uuid.server configuration value in opensearch_dashboards.yml and ensure OpenSearch Dashboards has sufficient permissions to read / write to this file. Error was: EROFS

In addition, I can find no example or documentation showing the configuration variable (uuid.server) mentioned in the error message.

To Reproduce
Steps to reproduce the behavior:

  1. I added the following stanza to my user-values.yaml file:
securityContext:
  readOnlyRootFilesystem: true
  1. Deploy OpenSearch Dashboards using Helm (and pointing to the user-values.yaml file)
  2. I can see the OpenSearch Dashboards pod starting up but fails fairly early with the error messages shown above.
  3. If I remove that stanza, OpenSearch Dashboards comes up without problems.

Expected behavior
I expected OpenSearch Dashboards to come up without problems. I would also expect to find some mention of the configuration variable (uuid.server) in the documentation or sample opensearch-dashboards.yml files.

Chart Name
I've seen this error with using both OpenSearch Dashboards version 1.3.5 (Helm chart version 1.5.1) and 2.4.1 (Helm chart version 2.7.0).

Host/Environment (please complete the following information):

  • Helm Version: 3.7.0
  • Kubernetes Version: 1.22.3

Additional context

  • I notice that readOnlyRootFilesystem key is included (on line 95) in the Helm charts values.yml file but commented out.
  • I also noticed is that if I omit the readOnlyRootFilesystem key (which allows OpenSearch Dashboards to come up), and SSH onto the running OpenSearch Dashboard pod, the file /usr/share/opensearch-dashboards/data/uuid and owned by user "opensearch-dashboards" (UID:1000) rather than root.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestquestionFurther information is requested

    Type

    No type

    Projects

    Status

    📦 Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions