Connect on Openshift: failure during startup due to `chown <DataDir>`
Closed this issue · 1 comments
pat-s commented
We've built an image which works around all non-openshift compliant startup procedures. We're currently stuck at the step when Connect tries to chown DataDir
.
In Openshift, non-privileged users are not allowed to do this.
[...]
Creating Python environment cache directory: [...]
Error: Unable to apply the configuration: lchown <DataDir`/python-environments: operation not permitted
Is there any way to avoid this chown
call? According to the documentation, it should be possible to run Connect rootless in k8s. Yet the above built-in command seems to prevent this and cannot be modified/turned off right now.
pat-s commented
Setting securityContext: null
for both occurrences and letting Openshift create it itself did the trick.