Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
mesh.lock could not be writen on OpenShift #506
Gentics Mesh Version, operating system, or hardware.
In Openshift any Pod runs with a random user id. So writing mesh.lock during startup fails
/data, /config, /elasticsearch and /tmp (via MESH_TEMP_DIR) is writable via emptyDir volumes.
But mesh still tries to write /mesh/mesh.lock which is not possible.
oc new-app gentics/mesh
Expected behaviour and actual behaviour
It should be written to MESH_TEMP_DIR by default IMHO
Is there any undocumented env var for setting the lock file location?
Thanks for the issue. The path to every file, folder that is managed by Gentics Mesh should be configurable. I'll try to squeeze the change into the next 0.24.x release. There is currently no setting for this. The path to the lock file is always relative to the current working directory.
I solved the problem on my own by writting a new Dockerfile which is more suitable for Openshift
The trick is to move everything out of the working directory so that we can bind-mount an emptyDir volume in OpenShift which makes it writable.
Anyway MESH_LOCK_PATH solves the problem also.