-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Arbiter crashloop on chart 8.0.0+ #24597
Comments
Adding here, I was able to get things running by including
in |
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. |
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. |
Name and Version
bitnami/mongodb-sharded:8.0.2
What architecture are you using?
amd64
What steps will reproduce the bug?
I believe I'm running into the same bug as this previous issue, but with the sharded chart. See bitnami/containers#63885
My values.yaml look like:
What is the expected behavior?
The arbiter should start successfully.
What do you see instead?
Crashloop with the error
mkdir: cannot create directory '/bitnami/mongodb/data/db': Read-only file system
If I update the arbiter to include
I see
mkdir: cannot create directory '/bitnami/mongodb/data/db': Permission denied
instead.Additional information
It looks like the same
volumeMounts
entry may be missing from the arbiter'sstatefulset.yaml
, as in the other bug.The text was updated successfully, but these errors were encountered: