EAS does not work with readOnlyRootFilesystem

[albertschwarzkopf]

trafficstars

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

[travisghansen]

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?

[albertschwarzkopf]

@travisghansen thanks for your answer. I have tried with additional volume mounted at /tmp. But this has not worked.