Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitnami/discourse] Setting readonlyFilesystem to true, restart pods #31463

Open
divyanshch2019 opened this issue Jan 17, 2025 · 0 comments
Open
Assignees
Labels
tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@divyanshch2019
Copy link

Name and Version

bitnami/discourse 7.0.0

What architecture are you using?

amd64

What steps will reproduce the bug?

Install the helm chart with the following values.yaml

containerSecurityContext:
 enabled: true
 allowPrivilegeEscalation: false
 readOnlyRootFilesystem: true

Are you using any custom parameters or values?

securityContext:
 runAsNonRoot: true
 runAsUser: 1000
 runAsGroup: 1000
 seccompProfile:
  type: RuntimeDefault

What is the expected behavior?

The discourse pod should run without any errors

What do you see instead?

/opt/bitnami/scripts/libpostgresqlclient.sh: line 53: cannot create temp file for here-document; Read-only file system

Additional information

No response

@divyanshch2019 divyanshch2019 added the tech-issues The user has a technical issue about an application label Jan 17, 2025
@github-actions github-actions bot added the triage Triage is needed label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

2 participants