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/mongodb-sharded] cannot create directory '/bitnami/mongodb/data/db' in arbiter pod #30979

Closed
shuhengyang opened this issue Dec 11, 2024 · 3 comments
Assignees
Labels
mongodb solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@shuhengyang
Copy link

shuhengyang commented Dec 11, 2024

Name and Version

bitnami/mongodb-sharded

What architecture are you using?

None

What steps will reproduce the bug?

helm install mongodb  bitnami/mongodb-sharded --version 9.1.0 -f value.yaml 

Are you using any custom parameters or values?

persistence.enables: false

What do you see instead?

arbiter  pod ERROR: mkdir: cannot create directory '/bitnami/mongodb/data/db': Read-only file system
@shuhengyang shuhengyang added the tech-issues The user has a technical issue about an application label Dec 11, 2024
@github-actions github-actions bot added the triage Triage is needed label Dec 11, 2024
@carrodher
Copy link
Member

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:

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

Copy link

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

@github-actions github-actions bot added the stale 15 days without activity label Dec 27, 2024
Copy link

github-actions bot commented Jan 1, 2025

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@github-actions github-actions bot added the solved label Jan 1, 2025
@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mongodb solved stale 15 days without activity tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

3 participants