-
Notifications
You must be signed in to change notification settings - Fork 44
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
EAS does not work with readOnlyRootFilesystem #189
Comments
Hmm, let me take a look and see if I can figure out where it’s writing to. Have you made a rw /tmp in your deployment? |
@travisghansen thanks for your answer. I have tried with additional volume mounted at /tmp. But this has not worked. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi I have patched your default securityContext (which is defined in your helm chart).
But with
readOnlyRootFilesystem: true
EAS will not start. Even I do not see any error message. Just "CrashLoopBackOff" at start. Without above setting it is working.
Is it really necessary to write to the root volume? Maybe better to add additional volume for write operations?
Thanks and best regards
The text was updated successfully, but these errors were encountered: